Multi-chassis fabric-backplane enterprise servers

ABSTRACT

Multi-chassis fabric-backplane enterprise servers include a plurality of chassis managed collectively to form one or more provisioned servers. A central client coordinates gathering of provisioning and management information from the chassis, and arranges for distribution of control information to the chassis. One of the chassis may perform as a host or proxy with respect to information and control communication between the client and the chassis. Server provisioning and management information and commands move throughout the chassis via an Open Shortest Path First (OSPF) protocol. Alternatively, the client may establish individual communication with a subset of the chassis, and directly communicate with chassis in the subset. Server provisioning and management information includes events generated when module status changes, such as when a module is inserted and becomes available, and when a module fails and is no longer available. Each chassis includes a switch fabric enabling communication between chassis modules.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/057,035 (Docket No. F7.2004.13, filed Feb. 12, 2005) entitledMULTI-CHASSIS FABRIC-BACKPLANE ENTERPRISE SERVERS and now U.S. Pat. No.7,873,693; U.S. Pat. No. 7,873,693 claimed the benefit of the followingapplications: U.S. Provisional Patent Application Ser. No. 60/544,916(Docket No. F7.2003.01, filed Feb. 13, 2004) entitled DYNAMICALLYPROVISIONABLE DISTRIBUTED VIRTUAL SERVERS, U.S. Provisional PatentApplication Ser. No. 60/563,222 (Docket No. F7.2004.02, filed Apr. 17,2004) entitled DYNAMICALLY PROVISIONABLE DISTRIBUTED VIRTUAL SERVERS,U.S. Provisional Patent Application Ser. No. 60/603,250 (Docket No.F7.2004.07, filed Aug. 20, 2004) entitled INSTANTIATION AND MANAGEMENTOF FABRIC-BACKPLANE ENTERPRISE SERVERS, U.S. Provisional PatentApplication Ser. No. 60/650,707 (Docket No. F7.2004.20, filed Feb. 7,2005) entitled CLASS INSTANCE RELATIONSHIP QUERY WITH OPTIONALCONSTRAINTS, U.S. Provisional Patent Application Ser. No. 60/651,027(Docket No. F7.2004.21, filed Feb. 7, 2005) entitled DYNAMIC USERINTERFACE SPECIFICATION FOR A PREDETERMINED INTERFACE ENGINE, and U.S.Provisional Patent Application Ser. No. 60/651,026 (Docket No.F7.2004.22, filed Feb. 7, 2005) entitled DURABLE QUERY REGISTRATION WITHREAL TIME RESPONSE; this application is also a continuation-in-part ofthe following applications: U.S. patent application Ser. No. 10/889,468(Docket No. F7.2004.03, filed Jul. 12, 2004) entitled FABRIC-BACKPLANEENTERPRISE SERVERS, U.S. patent application Ser. No. 10/889,467 (DocketNo. F7.2004.04, filed Jul. 12, 2004) entitled CLIENT-SERVER ANDAPPLICATION MODELS IN FABRIC-BACKPLANE ENTERPRISE SERVERS; and U.S.patent application Ser. No. 10/889,469 (Docket No. F7.2004.05, filedJul. 12, 2004) entitled COMPUTE RESOURCES FOR FABRIC-BACKPLANEENTERPRISE SERVERS; and wherein all of the foregoing applications areherein incorporated by reference for all purposes.

This application is related to the following applications co-filed Feb.12, 2005: U.S. patent application Ser. No. 11/057,116 (Docket No.F7.2004.06) entitled FABRIC-BACKPLANE ENTERPRISE SERVERS WITH VNICS ANDVLANS, U.S. patent application Ser. No. 11/057,048 (Docket No.F7.2004.17) entitled PROVISIONING AND MANAGEMENT OF FABRIC-BACKPLANEENTERPRISE SERVERS, U.S. patent application Ser. No. 11/057,120 (DocketNo. F7.2004.17B) entitled PROVISIONING AND MANAGEMENT OFFABRIC-BACKPLANE ENTERPRISE SERVERS, U.S. patent application Ser. No.11/057,113 (Docket No. F7.2004.08) entitled REAL TIME PROVISIONING ANDMANAGEMENT OF FABRIC-BACKPLANE ENTERPRISE SERVERS, U.S. patentapplication Ser. No. 11/057,038 (Docket No. F7.2004.08B) entitled REALTIME PROVISIONING AND MANAGEMENT OF FABRIC-BACKPLANE ENTERPRISE SERVERS,U.S. patent application Ser. No. 11/057,121 (Docket No. F7.2004.08C)entitled REAL TIME PROVISIONING AND MANAGEMENT OF FABRIC-BACKPLANEENTERPRISE SERVERS, U.S. patent application Ser. No. 11/057,037 (DocketNo. F7.2004.09) entitled FABRIC-BACKPLANE ENTERPRISE SERVERS WITH VNICSAND VLANS, U.S. patent application Ser. No. 11/057,036 (Docket No.F7.2004.09B) entitled FABRIC-BACKPLANE ENTERPRISE SERVERS WITH VNICS ANDVLANS, U.S. patent application Ser. No. 11/057,119 (Docket No.F7.2004.09C) entitled FABRIC-BACKPLANE ENTERPRISE SERVERS WITH VNICS ANDVLANS, U.S. patent application Ser. No. 11/057,112 (Docket No.F7.2004.09D) entitled FABRIC-BACKPLANE ENTERPRISE SERVERS WITH VNICS ANDVLANS, U.S. patent application Ser. No. 11/057,046 (Docket No.F7.2004.10) entitled LINK AGGREGATION GROUPS IN FABRIC-BACKPLANEENTERPRISE SERVERS, U.S. patent application Ser. No. 11/057,114 (DocketNo. F7.2004.11) entitled RAPID IP/MAC ADDRESS TAKEOVER VIA FORWARDINGTABLE UPDATES, U.S. patent application Ser. No. 11/057,034 (Docket No.F7.2004.11B) entitled RAPID IP/MAC ADDRESS TAKEOVER VIA FORWARDING TABLEUPDATES, and U.S. patent application Ser. No. 11/057,117 (Docket No.F7.2004.13B) entitled MULTI-CHASSIS FABRIC-BACKPLANE ENTERPRISE SERVERS;and wherein all of the foregoing applications are herein incorporated byreference for all purposes.

FIELD OF THE INVENTION

The present invention relates generally to interprocess and inter-modulecommunications in servers and server clusters. More specifically, itrelates to the organization, provisioning, management, andinteroperation of compute, storage, and network resources to enhancedatacenter availability, efficiency, and utilization.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1A illustrates a conceptual representation of an embodiment of anES system.

FIG. 1B illustrates a conceptual representation of selected details ofdata transfer in an embodiment of an ES system.

FIG. 2 illustrates various example embodiments of packet and processdata flow in an ES embodiment.

FIG. 3A illustrates selected aspects of an embodiment of packettransmission and reception in an ES embodiment.

FIG. 3B illustrates selected aspects of an embodiment of packet and cellprioritized transmission in an ES embodiment.

FIG. 4A illustrates selected aspects of an embodiment of a SystemIntelligence Module (SIM) configured as a pluggable module including aSystem Control Module (SCM) and an associated Switch Fabric Module(SFM).

FIG. 4B illustrates selected aspects of an embodiment of a ProcessorMemory Module (PMM) configured as a pluggable module.

FIG. 4C illustrates selected aspects of an embodiment of a NetworkModule (NM) configured as a pluggable module.

FIG. 4D illustrates selected aspects of an embodiment of a Fibre ChannelModule (FCM) configured as a pluggable module.

FIG. 4E illustrates selected aspects of an embodiment of an OffLoadBoard (OLB) configured as a pluggable module.

FIG. 5A illustrates selected aspects of embodiments of SoftWare (SW)layers for executing on application processor resources in an ESembodiment.

FIG. 5B illustrates selected aspects of embodiments of SW layers forexecuting on management processor resources in an ES embodiment.

FIG. 5C illustrates selected aspects of embodiments of SW layers forexecuting on module-level configuration and management processorresources in an ES embodiment.

FIG. 6A illustrates selected aspects of a logical view of an embodimentof a plurality of virtual Network Interface Controllers (VNICs), alsoknown as virtualized Network Interface Cards.

FIG. 6B illustrates selected aspects of a logical view of an embodimentof VNIC transmit queue organization and prioritization.

FIG. 6C illustrates selected aspects of a logical view of an embodimentof transmit output queue organization and prioritization.

FIG. 6D illustrates selected aspects of a logical view of an embodimentof receive input queue organization and prioritization.

FIG. 6E illustrates selected aspects of a logical view of an embodimentof VNIC receive queue organization and prioritization.

FIG. 7A illustrates selected aspects of an embodiment of a Virtual InputOutput Controller (VIOC).

FIG. 7B illustrates selected aspects of egress operation of anembodiment of a Virtual Input Output Controller (VIOC).

FIG. 7C illustrates selected aspects of ingress operation of anembodiment of a VIOC.

FIG. 8A illustrates selected aspects of an embodiment of an egresslookup key and result entries.

FIG. 8B illustrates selected aspects of an embodiment of an ingresslookup key and entry.

FIGS. 9A and 9B illustrate a Hardware Resources view and a ProvisionedServers and Switch view of an embodiment of an ES system, respectively.

FIG. 9C illustrates an operational view of selected aspects ofprovisioning and management SW in an ES embodiment.

FIG. 10 illustrates a conceptual view of an embodiment of a ServerConfiguration File (SCF) and related SCF tasks.

FIG. 11 illustrates selected aspects of an embodiment of serveroperational states and associated transitions.

FIGS. 12A and 12B are flow diagrams illustrating selected operationalaspects of real time server provisioning and management in an ESembodiment.

FIG. 13A is a state diagram illustrating processing of selectedBaseboard Management Controller (BMC) related commands in an ESembodiment.

FIG. 13B illustrates selected operational aspects of single and dual PMMlow-level hardware boot processing in an ES embodiment.

FIG. 14 illustrates a conceptual view of selected aspects of embodimentsof Internet Protocol (IP) and Media Access Control (MAC) addressfailover data structures and associated operations.

FIG. 15 illustrates a flow diagram of an embodiment of rapid IP addresstakeover.

FIG. 16 illustrates an embodiment of a multi-chassis fabric-backplane ESsystem.

FIG. 17 illustrates an embodiment of two variations of multi-chassisprovisioning and management operations.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess, an apparatus, a system, a composition of matter, a computerreadable medium such as a computer readable storage medium or a computernetwork wherein program instructions are sent over optical or electroniccommunication links. In this specification, these implementations, orany other form that the invention may take, may be referred to astechniques. In general, the order of the steps of disclosed processesmay be altered within the scope of the invention.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Introduction

This introduction is included only to facilitate the more rapidunderstanding of the Detailed Description. The invention is not limitedto the concepts presented in the introduction, as the paragraphs of anyintroduction are necessarily an abridged view of the entire subject andare not meant to be an exhaustive or restrictive description. Forexample, the introduction that follows provides overview informationlimited by space and organization to only certain embodiments. There arein fact many other embodiments, including those to which claims willultimately be drawn, which are discussed throughout the balance of thespecification. As is discussed in more detail in the Conclusions, theinvention encompasses all possible modifications and variations withinthe scope of the issued claims, which are appended to the very end ofthe issued patent.

Multi-chassis fabric-backplane enterprise servers include a plurality ofchassis managed collectively to form one or more provisioned servers. Acentral client coordinates gathering of provisioning and managementinformation from the chassis, and arranges for distribution of controlinformation to the chassis. One of the chassis may perform as a host orproxy with respect to information and control communication between theclient and the chassis. Server provisioning and management informationand commands move throughout the chassis via an Open Shortest Path First(OSPF) protocol. Alternatively, the client may establish individualcommunication with a subset of the chassis, and directly communicatewith chassis in the subset. Server provisioning and managementinformation includes events generated when module status changes, suchas when a module is inserted and becomes available, and when a modulefails and is no longer available. Each chassis includes a switch fabricenabling communication between chassis modules.

A hybrid server/multi-layer switch system architecture, referred tohereinafter as the Enterprise Fabric (EF) architecture, forms the basisfor a number of Enterprise Server (ES) chassis embodiments. Within eachES embodiment includes one or more Processor Memory Modules (PMMs, eachhaving a symmetric multiprocessor complex), one or more Network Modules,and a System Control Module (SCM). The SCM includes a cellifiedswitching-fabric core (SF) and a System Intelligence Module (SIM).

Each PMM has one or more resident Virtual IO Controller (VIOC) adapters.Each VIOC is a specialized Input/Output (I/O) controller that includesembedded layer-2 forwarding and filtering functions and tightly couplesthe PMM to the SF. Thus the layer-2 switch functionality within the ESchassis is distributed over all of the SCM, NM, and PMM modules. Throughthe use of VIOC/VNIC device drivers, host operating system software(Host O/S) running on the PMMs is presented with a plurality of VirtualNetwork Interface Cards (VNICs). In some embodiments, each VNIC behavesas a high-performance Ethernet interface at the full disposal of theHost O/S. In other embodiments, at least some of the VNICs behave ashigh-performance Fibre Channel Host Bus Adapters.

The SIM is responsible for provisioning and overall system management.Via system control and management processes running on the SIM, theserver and switch functionality of the ES chassis are provisioned viaconfiguration files in accordance with respective requirements specifiedby server and network administrators. Configurable parameters for eachserver include the number of processors, memory, the number of VNICs,and VNIC bandwidth. Configurable parameters for the network includeVirtual LAN (VLAN) assignments for both Network Module ports and VNICsand Link Aggregation Group (LAG) definitions.

An ES system may be operated as one or more provisioned servers, each ofthe provisioned servers including capabilities as identified by acorresponding set of specifications and attributes, according to variousembodiments. Typically the specifications (or constraints) andattributes are specified with a Server Configuration File. An ES systemmay be provisioned into any combination and number of servers accordingto needed processing and I/O capabilities. Each of these servers mayinclude distinct compute, storage, and networking performance.Provisioned servers may be managed similar to conventional servers,including operations such as boot and shutting down.

One or more VNICs provide for communication among modules of EnterpriseServer (ES) embodiments via a switch fabric dataplane. Processesexecuting on compute complexes of the servers exchange data as packetsor messages by interfaces made available through VNICs. The VNICsfurther provide for transparent communication with network and storageinterfaces. VNIC provisioning capabilities include programmablebandwidth, priority scheme selection, and detailed priority control(such as round-robin weights). In some embodiments, VNICs areimplemented in Virtual Input/Output Controllers (VIOCs). In anotheraspect, Virtual Local Area Networks (VLANs) enable access to Layer-2(L2) and selected Layer-3 (L3) network functions while exchanging thepackets and messages. VLAN identification is provided in each VNIC, andVLAN processing is partially performed in VIOCs implementing VNICs.

The compute complexes and interfaces are typically configured aspluggable modules inserted into a backplane included in a chassis. Theswitch fabric dataplane (sometimes simply referred to as “a dataplane”)is accessible via the backplane (serving as a replacement for aconventional backplane bus), and hence ES embodiments are known as“fabric-backplane” enterprise servers. Various ES embodiments arecomprised of varying numbers and arrangements of modules.

The EF architecture provides for provisioning virtual servers (alsoknown as server-instances) with included virtual networks fromunderlying ES hardware and software resources. The EF architecture isapplicable to application scenarios requiring dynamic combinations ofcompute, network, and storage performance and capabilities, and is aunifying solution for applications requiring a combination ofcomputation and networking performance Resources may be pooled, scaled,and reclaimed dynamically for new purposes as requirements change, usingdynamic reconfiguration of virtual computing and communication hardwareand software. This approach offers the advantages of reduced cost, asprovisioning is “just-right” rather than over-provisioned. In addition,dynamic configuration allows for quick performance or scalemodifications.

The EF architecture provides a radically different underlying serverarchitecture compared to traditional multi-way Symmetric MultiProcessor(SMP) servers, including integrated fabric interconnectivity to enablehigh-bandwidth, low-latency I/O operation. Processing and I/O throughputare virtualized, providing scalable, coordinated resources. Partitioningand fail-over are hardware supported, including mechanisms for treatingmultiple virtual servers as a single managed entity, resulting in newhigh availability clustering and multi-site fail-over capabilities.Compared to a current network switch, networking capabilities areextended, including efficient Remote Direct Memory Access (RDMA) andflexible resource pooling. Virtualized fabric services, such as ServerLoad Balancing (SLB), Secure Sockets Layer (SSL) protocols includingTransport Layer Security (TLS) variants, eXtensible Markup Language(XML), and so forth, are also provided.

In some embodiments, a data center or other installation implemented inaccordance with the EF architecture will include one or more ES chassis.In a first embodiment, the ES chassis capabilities include an 8-way SMPpartition-configurable compute complex. These compute resources includea plurality of 64-bit x86 processing elements. The ES chassis hardwareconfiguration is compatible with execution of software operating systemssuch as Linux and Microsoft Windows. Processing elements in the ESchassis are coupled to a low-latency high-bandwidth interconnect fabricvia virtualized I/O functions, providing for efficient communicationbetween processing elements and with network and fibre channelinterfaces coupled to the fabric. The virtualized I/O functions aredistributed throughout the plurality of processing elements. Among thevirtualized I/O functions, the ES chassis includes VNICs and virtualizedHost Bus Adaptors (VHBAs). Via these VNICs and VHBAs, the processingelements can selectively communicate with external networks coupled toany of several high-performance network interfaces (up to three 10 GbEthernet interfaces, or thirty 1 Gb Ethernet interfaces, in the firstembodiment) and with several high-performance 2 Gb Fibre Channelinterfaces (up to eight in the first embodiment). Each VNIC/VHBA can beindividually configured such that it appears to be coupled to amulti-port switch coupled to other of the VNICs/VHBA and to thenetwork/storage interfaces. Alternatively, each VNIC/VHBA can beconfigured such that it appears to be directly coupled to one of thenetwork/storage interfaces. Additional processing capabilities may beprovided in the chassis in the form of offload cards (or pluggableboards or modules) supporting virtualized services, such as SLB, SSL,and XML processing.

The ES chassis is further configured with capabilities to provide for ahigh availability system, including modular components, hot-swap ofcomponents, and fully redundant components. Other high availabilitycapabilities include multi-site fail-over and mainframe classReliability, Availability, and Serviceability (RAS) features.

An ES system may be operated as one or more provisioned servers, each ofthe provisioned servers including capabilities as identified by acorresponding set of specifications and attributes, according to variousembodiments. Typically the specifications (or constraints) andattributes are specified with an SCF (see the SCF and Related Taskssection, elsewhere herein). An ES system may be provisioned into anycombination and number of servers according to needed processing and I/Ocapabilities. Each of these servers may include distinct compute,storage, and networking performance. Provisioned servers may be managedsimilar to conventional servers, including operations such as boot andshutting down (see the Server Operational States section, elsewhereherein).

The EF architecture further includes a Graphical User Interface (GUI)for configuration management. The GUI may be provided via a web browser,a network-based Java client, or some other related mechanism, accordingto various embodiments. The GUI provides role-based access and divisionof functions, and may be used as a single point of management for all EFsystem functions. System management personnel may use the GUI to controlEF virtualized configuration and provisioning settings. Resource poolingand allocation of Central Processing Unit (CPU) and IO capabilities maybe dynamically altered without requiring physical changes or re-cabling.Network and storage capabilities may be similarly dynamically modified,including Network Interface Controller (NIC), Host Bus Adaptor (HBA),and bandwidth resources. Redundancy, fail-over and other RAScapabilities may also be configured via the GUI, including specificmulti-site configuration information. Various embodiments may alsoinclude a Command Line Interface (CLI) with functions and capabilitiessimilar to the GUI.

The GUI further provides functions for monitoring various aspects of thehardware and software performance and behavior of systems including eachES chassis. The monitoring functions are available for inspection ofoperations at several levels in the system, from top-level applicationperformance to low-level network interconnect metrics.

The GUI provides hooks for integration of the functions provided thereininto higher-level application software and standard applications,allowing for flexibility in specifying and monitoring the EF systemconfiguration.

EF configuration management and monitoring may also be performed viaother mechanisms. Alternate mechanisms include one or more command lineinterfaces, a scripting interface, and remote network-centric interfacesusing standard capabilities provided for in Simple Network ManagementProtocol (SNMP) and Remote MONitoring (RMON).

Systems including EF capabilities may also provide for upgrades toinstalled software, including operating system software, applicationsoftware, driver-level software, and firmware software. The upgrades mayinclude updates to address security issues, to enable new or expandedfunctionality, or to repair incorrect operation (a “bug fix”). A varietyof sources may provide upgrades, including EF vendors, or vendors ofsoftware installed or used in EF -based systems. Additionally,Independent Software Vendor (ISV) certifications of software associatedwith EF-based systems may also be performed.

Illustrative application usage scenarios include a first usage scenarioincluding a first configuration adapted to replace a server (having anOperating System selected from a list including but not limited to Unix,Linux, Windows, etc.) or a collection of such servers. The firstconfiguration provides for virtualization of data center capabilities,resource pooling, and consolidation of functions otherwise performed ina plurality of heterogeneous devices. Computing, networking, andservices are completely virtualized, enabling dynamic deployment,scaling, and reclamation according to changing application requirements.Significant savings in capital and operating expense result.

A second usage scenario includes a second configuration adapted for I/Ointensive applications. The second configuration provides high-bandwidthand low-latency storage and networking capabilities, enabling newclasses of applications using fewer infrastructure components thancurrently possible. The high-bandwidth and low-latency capabilities areenabled in part by use of a high-bandwidth, low-latency fabric.Efficient intra-chassis communication is provided for in a transparentmanner, enabling increased I/O bandwidth and reduced latency compared toexisting solutions.

A third usage scenario includes a third configuration adapted forconsolidating tiers in a data center application. The thirdconfiguration provides for collapsing the physical divisions in present3-tier data centers, enabling solutions with fewer servers, a smallernumber of network switches, and reduced needs for specializedappliances. The concepts taught herein provide for completelyvirtualized computing, networking, and services, in contrast to existingsolutions addressing tiered data systems. Dynamic configuration enablespooling of resources and on-the-fly deploying, scaling, and reclaimingof resources according to application requirements, allowing for reducedinfrastructure requirements and costs compared to existing solutions.

A fourth usage scenario includes a fourth configuration adapted forenhanced high availability, or RAS functionality, including multi-sitefail-over capabilities. The fourth configuration provides for newredundancy and related architectures. These new architectures reduceset-up and configuration time (and cost), and also decrease on-goingoperating expenses. Modular components of the ES chassis are hot-swapcompatible and all EF systems are configured with fully redundantcomponents, providing for mainframe-class RAS functionality. Reducednetworking latency capabilities enable enhanced multi-site fail-overoperation.

The concepts taught herein thus enable simple, fast, straightforward,low-effort deployment of systems configured and provisioned forefficient execution of heterogeneous mixes of applications requiringvarying computing, networking, and I/O processing resources. Applicationfail-over architectures are also readily enabled with little or noadditional hardware, according to further dynamic partitioning features.Accordingly, Information Technology (IT) operations are reduced incomplexity and cost.

The concepts taught herein consolidate multiple devices and tiers indata center operations, requiring fewer servers (in type and quantity),reduced supporting hardware, and smaller infrastructure outlays comparedto systems of the current art. Significant reductions in the total costof ownership are thus provided for by the concepts taught herein.

The concepts taught herein, ensure highly reliable and availablecompute, network, storage, and application resources while alsodramatically improving storage and networking performance andreliability. True multi-site fail-over and disaster recovery arepossible by use of the concepts taught herein, enabling new classes ofI/O and high availability applications.

Enterprise Server System

FIG. 1A illustrates System 100A, a conceptual representation of anembodiment of an ES system. The system includes a particular ES chassisembodiment, ES1 110A, which is coupled to various other systems,including Fibre Channel Storage Network 106, Generic Packet Network 107,and Ethernet Storage Network 108. Fibre Channel Storage Network 106provides mass storage via a collection of disks organized, for example,as a Storage Area Network (SAN). Generic Packet Network 107 conceptuallyincludes arbitrary combinations of Local Area Network (LAN), Metro AreaNetwork (MAN), and Wide Area Network (WAN) networks and typicallyincludes Ethernet and Ethernet derivative links for coupling to Internet101, an arbitrary number and arrangement of Client machines or servers,represented as Client 102 and Client 103, as well as an arbitrary numberand arrangement of Personal Computers (PCs) or Workstations, representedas PC 104 and PC 105. Ethernet Storage Network 108 provides mass storagevia a collection of disks organized in a Network Attached Storage (NAS)or Small Computer System Interface over Transmission ControlProtocol/Internet Protocol (iSCSI) fashion.

ES1 110A includes a central I/O SFM (SFM 180) providing a switch fabricdataplane coupling for FCMs 120, NMs 130, SCMs 140, PMMs 150 (also knownas Application Processor Modules), and OLBs 160, also known as OffloadModules (OLMs) or AppLication Modules (ALMs). Cell-based communicationis carried out over the switch fabric dataplane between theaforementioned elements coupled to it. In other words, the fabricfunctions as a cell-based switch. FCMs 120 include Fibre ChannelInterfaces (FCIs) for coupling to Fibre Channel standard storage devicesand networks (such as SANs). NMs 130 include interfaces to standardnetwork infrastructures. PMMs 150 include compute elements for executionof Application, Driver, and Operating System (OS) processes, via SMPclusters illustrated conceptually as SMP 151. A configurable CoherencySwitch Fabric and Interconnect (CSFI 170) is included for partitioningor combining the CPU and Randomly Accessible read/write Memory (RAM)resources of PMMs 150. OLBs 160 include compute elements for executionof service processes, via various service acceleration modules. Serviceacceleration modules include SLB accelerator 161, SSL accelerator 162,and XML accelerator 163. SCMs 140 include compute elements for providingsystem management, controlplane (L2/L3 bridging and routing, forexample), and load balancing processing for SFM 180 and the elementscoupled to it. PMMs 150 also include FCIs for coupling to mass storagesystems, such as Optional Local Disks 111-112, or SAN systems includingmass storage.

In operation, Application, Driver, and OS processes are executed on PMMs150 via CPU and RAM elements included in SMP 151. At least some of thedata consumed and produced by the processes is exchanged in packetsformatted as cells for communication on SFM 180. The data may includenetwork data exchanged with Generic Packet Network 107 via NMs 130, andstorage data exchanged with Ethernet Storage Network 108 via NMs 130 orFibre Channel Storage Network 106 via FCMs 120. The data may alsoinclude service data exchanged with OLBs 160 and SCMs 140, and otherApplication, Driver, or OS data exchanged with other elements of PMMs150.

Data communicated on SFM 180 is not limited to data exchanged with PMMs150, but may also include data communicated between any of the modules(or fabric clients) coupled to the fabric. For example, one NM mayforward packets to itself or to another NM via the fabric. An NM mayalso exchange packets with an OLB for processing via the fabric. SCMs140 may also exchange configuration and forwarding update informationwith VIOCs via VIOC Control Protocol (VIOC-CP) packets via the fabric.In some embodiments, SCMs 140 may also exchange selected systemmanagement, controlplane, and load balancing information with allmodules coupled to the fabric via in-band packets communicated on thefabric.

In one embodiment, in conjunction with the VNIC functionality mentionedpreviously, a modified Ethernet Driver provides the illusion of localNIC functionality to Application, Driver, and OS processes locallyexecuting on any of SCMs 140, PMMs 150, and OLBs 160. The NICfunctionality can be configured to either appear to be coupled to aswitch coupled to other NICs or appear to be coupled directly to one ofthe networking interfaces included on NMs 130. In another embodiment,this technique may be used to access networked storage devices (i.e.,NAS subsystems) via the NMs 130.

As illustrated conceptually, SFM 180 includes a redundant pair offabrics, with one of the pair typically configured as a Primary Fabric,while the other fabric is typically configured as a Redundant Fabric.SCM-Fabric coupling 149 represents two fabric dataplane couplings, afirst Primary Coupling between a Primary SCM of SCMs 140 and the PrimaryFabric, and a Redundant Coupling between a Redundant SCM of SCMs 140 andthe Redundant Fabric. In one mode of operation, all dataplane traffic iscarried on the Primary Fabric, managed by the Primary SCM, while theRedundant Fabric and the Redundant SCM are maintained in a hot-standbymode.

Further dataplane couplings to SFM 180 are illustrated conceptually asFCM-Fabric coupling 129, NM-Fabric coupling 139, PMM-Fabric coupling159, and OLB-Fabric coupling 169. In FIG. 1, each coupling is abstractlyportrayed as a single line between each group of modules and the switchfabric. It will be understood that for the FCM, NM, and OLB modules,each module instance has a Primary Fabric coupling and a RedundantFabric coupling. For the PMM, each PMM instance has two Primary Fabriccouplings and two Redundant Fabric couplings.

All of the modules coupled to SFM 180 (FCMs 120, NMs 130, SCMs 140, PMMs150, and OLBs 160) include fabric interface communication units forexchanging data as cells on the fabric. The details of this dataexchange are described in more detail elsewhere herein.

In an illustrative embodiment, the components of ES1 110A are includedon a plurality of pluggable modules adapted for insertion into andremoval from a backplane while the server is powered-up and operational(although software intervention to cleanly shut down or start up variousprocesses or functions may be required). The backplane forms portions ofFCM-Fabric coupling 129, NM-Fabric coupling 139, CSFI-PMM coupling 179,PMM-Fabric coupling 159, and OLB-Fabric coupling 169. The Primary Fabricof SFM 180 and the associated Primary SCM of SCMs 140 are included onpluggable module Primary SIM as illustrated by SIMs 190. Similarly, theRedundant Fabric of SFM 180 and the associated Redundant SCM of SCMs 140are included on pluggable module Redundant SIM of SIMs 190. All of themodules of FCMs 120, NMs 130, PMMs 150, and OLBs 160 are also configuredas pluggable modules adapted for operation with the backplane.

Each PMM of PMMs 150 is physically-partitionable, i.e. configurable intoone or more physical partitions. The physical partitioning of PMMs 150and related modes of CSFI 170 are configured under program control. Forexample, PMMs 150 may be configured as a single SMP complex inconjunction with CSFI 170. The result is a first example of a physicalpartition. In a second example, each PMM of PMMs 150 may instead beconfigured individually as an independent SMP complex, resulting in aplurality of physical partitions, one for each PMM. In a third example,each PMM of PMMs 150 may instead be configured as a pair of SMPcomplexes, resulting in two physical partitions per PMM. In variousembodiments, CSFI 170 may be implemented as any combination of simpleinterconnect, coherency logic, and switching logic, operating inconjunction with any combination of interconnect and logic included onPMMs 150. Some of these embodiments are discussed in more detail laterherein.

ES1 110A, as illustrated, is representative of a number of embodimentsconfigured with various Modules to provide differing amounts of storageand network interface capability (connectivity and bandwidth), as wellas differing levels of compute capability (cycles and memory).Typically, each embodiment includes at least a redundant pair of SwitchFabrics and associated System Intelligence Modules (for communicationbetween Modules), at least one Processor Memory Module (for execution ofApplication, Driver, and OS processes), and at least one Network Module(for communication with external agents). Some embodiments mayoptionally further include any combination of additional Modules toprovide additional interface and compute capability, up to the physicallimits of the particular implementation. For example, additional NetworkModules may be included in an embodiment to provide additional networkbandwidth or connectivity. One or more Fibre Channel Modules may beincluded in an embodiment to provide additional storage bandwidth orconnectivity. Additional Processor Memory Modules may be included toprovide additional compute cycles or memory. One or more Offload Modulesmay be included to provide additional service compute cycles or memory,and these Offload Modules may each be individually configured with anycombination of SLB, SSL, and XML accelerators.

In the embodiments represented by ES1 110A, communication between theModules via SFM 180 is independent of the manner and arrangement of theModules. All of the Modules communicate as peers on SFM 180 andinterface to the fabric in a similar manner.

System 100A is also representative of a variety of system embodiments,for example, differing in the number, type, and arrangement of storageand network systems coupled to ES1 110A. For example, any combination ofOptional Local Disks 111-112 may be included. Generic Packet Network 107may include any combination of LAN, MAN, or WAN elements. FCMs 120 maybe coupled to a single SAN, or a plurality of SANs. NMs 130 may becoupled to a plurality of networks or storage systems. Couplings betweenES1 110A and other systems is limited only by the number and type ofinterfaces and physical couplings available according to implementation.

FIG. 1B illustrates System 100B, a conceptual representation of selecteddetails of data transfer in an embodiment of an ES system. An ES chassisembodiment, illustrated as ES1 110B, is coupled to Fibre Channel StorageNetwork 106 and Ethernet Network 107, as described elsewhere herein. Inthe illustrated embodiment, one module of each type (FCM 120A, NM 130A,PMM 150A, and OLB 160A) are coupled to Primary Switch Fabric Module180A, via FCM-Fabric coupling 129A, NM-Fabric coupling 139A, PMM-Fabriccouplings 159A/159A′, and OLB-Fabric coupling 169A, respectively. FCM120A provides interfaces for storage network couplings, including acoupling for Fibre Channel Storage Network 106. NM 130A providesinterfaces for network couplings, including a coupling for EthernetNetwork 107, coupled in turn to Client 102. In this illustrativescenario, PMM 150A is configured as a first and a second physicalpartition. The first physical partition includes SMP Portion P_(A) 152A,having RAM 153A, and is coupled by PMM-Fabric coupling 159A to thefabric dataplane. The second physical partition includes SMP PortionP_(A), 152A′, having RAM 153A′, and is coupled by PMM-Fabric coupling159A′ to the fabric dataplane. Note: several elements have been omittedfrom the figure for clarity, including the SCMs, the Redundant Fabric,the CSFI, and optional SANs.

Several illustrative data transfer paths are shown, includingClient-Server Data Exchange 115, Storage-Server Data Exchange 116,Client-Service Data Exchange 117, and Service Data Exchange 118. Eachpath illustrates the movement of data between two clients of the switchfabric. Consider now three embodiments, described from the perspectiveof these clients. In one embodiment, data is organized as packetstransferred via a stateless connection-free (and unreliable) protocol.In another embodiment, data is organized as messages, and transferredvia a connection-oriented reliable message protocol. In yet anotherembodiment, data is selectively organized as either packets or messages.

The underlying fabric transport process is transparent to the clientsand external devices coupled to the system and to most of the hostsoftware processes on the PMMs and OLBs. As described in more detailelsewhere herein, to external network devices, each port of each NM actsas a switch port of a virtualized high-performance L2/L3 switch. As willbe discussed in further detail elsewhere herein, the switch has advancedVLAN and classification functionalities. The VLAN functionality providesfor selectively coupling or isolating the network segments coupled toeach switch port. Each segment associated with an NM port may have oneor more external physical network devices as in any conventional networksegment. The classification functionality provides for specialforwarding treatments in accordance with a variety of attributes of theEthernet frames received from external network devices on the ports ofthe NMs. Select software processes running on the PMMs and OLBs areprovided the illusion that they are coupled via high-performanceEthernet network interfaces to dedicated ports of the VLAN-enabledswitch. Connectivity between the different network segments may beflexibly and arbitrarily configured through VLAN management.

In systems having FCMs, a virtualized fibre channel switch is similarlypresented to external fibre channel devices. Likewise, certain softwareprocesses running on the PMMs are provided the illusion they are coupledto the fibre channel switch via high-performance fibre channelinterfaces. Multiple VLANs and multiple fibre channel networks cansimultaneously co-exist on top of the fabric transport infrastructurewhile being completely logically separate and secure.

The underlying fabric transport process is discussed in more detailelsewhere herein, but it will now be briefly overviewed. The fabricsupports the transparent transport of both packets and messages. Here,“packets” refers to conventional Ethernet frames sent via someconnectionless protocol that does not have integral support for reliabledelivery. The term “messages” refers to one or more data transfers ofquasi-arbitrarily sized data blocks reliably delivered over a logicalconnection established between end-points. Packets are transported overthe fabric using “fabric packets,” while messages are transported overthe fabric using “fabric messages.” Both fabric packets and fabricmessages make use of highly similar fabric frames. A fabric packet iscomprised of a single fabric frame, sent over the fabric without anyconnection or reliable delivery support. In contrast, fabric messagesare comprised of (potentially quite long) sequences of fabric frames,sent over the fabric using a connection-oriented reliable deliveryprotocol. Some of the fabric frames of a fabric message are for transferof the message data blocks while other fabric frames are used forcontrol to set up and take down connections and to implement reliabledelivery (e.g., via handshake and re-delivery attempts).

Thus fabric messages require additional fabric frames for messagingcontrol beyond the fabric fames required to transport the message data.Furthermore, the fabric frames of fabric messages require additionalprocessing at the source and destination ends related to the managementof reliable delivery, connections, and the fragmentation (segmentation)and reassembly of data blocks. Nevertheless, the transport over thefabric of individual fabric frames is essentially the same for bothfabric messages and fabric packets. Since all sources and destinationson the fabric have support for processing fabric packets and fabricmessages, those of ordinary skill in the art will understand that all ofthe data exchange illustrations below that describe the transport ofpackets using fabric packets are equally applicable to the transport ofmessages using fabric messages.

The Ethernet frames of the packets to be transported over the fabric mayoriginate in external clients or devices coupled to the NM ports or fromwithin the various processing modules. During processing by the NM orthe VIOC, respectively, a fabric packet is formed to contain the data ofeach original Ethernet frame plus additional information to facilitatetransport over the fabric. During the fabric packet formation, theprotocol field (Ether-type) of the original Ethernet frame is examined.The fabric packet is generally labeled (tagged) in accordance with theEther-type and other information found in the original packet. E.g., ifthe original Ethernet frame is an IP type frame, the fabric packet isidentifiable as an “IP fabric packet.” IP fabric packets are evaluatedfor L3 forwarding (a.k.a. IP forwarding) based upon their includeddestination IP address. Otherwise, non-IP fabric packets are evaluatedfor L2 forwarding based upon their included MAC destination address(MACDA). L2/L3 forwarding is overviewed next.

During the fabric packet formation a forwarding decision is made thatdetermines a fabric destination address that is embedded in the fabricpacket. The embedded fabric destination address controls how the fabricpacket is delivered to destinations within the system. The fabricdestination address includes a specification for an egress port of theswitch fabric. When multiple sub-ports (corresponding to multiple L2 orL3 destination addresses) are associated with a single egress port, thefabric destination address will also include a fabric sub-address tospecify a particular one of the sub-ports.

The fabric packet is subsequently cellified (segmented into cells) andpresented to an ingress port of the switch fabric. Each cell includesthe fabric destination address and the cell is transferred by the switchfabric to the egress port specified by the fabric destination address.After being received by the module coupled to the specified egress port,the cells are reformed into a representation of the original Ethernetframe prior to presentation to the destination. If the module at theegress port has multiple sub-ports, the module will use the includedfabric sub-address to further direct the reformed Ethernet frame to thespecified sub-port.

In L2 forwarding, the VLAN assignment of the network port or processingmodule from which the original Ethernet frame was sourced is also usedwith the MACDA in determination of the fabric destination address. Thedetermination is by way of a lookup in an L2 Forwarding Information Base(L2 FIB). As discussed elsewhere herein, an L2 FIB is implemented foreach VIOC and NM in the system using any combination of TCAM/SRAMstructures and search engines, according to embodiment. The L2forwarding decision is thus implemented completely within the modulewhere the original Ethernet frame was sourced and the next fabricdestination is the module most directly associated with the MACDA of theoriginal Ethernet frame.

General L3 forwarding (i.e., to destinations beyond the IP sub-net ofthe source IP) requires access (on the same L2 sub-net as the source) toat least one gateway IP interface and associated L3 FIB. The number andlocation of gateway IP interfaces and L3 FIBs varies by embodiment. In afirst L3 embodiment, a gateway IP interface and L3 FIB is implementedexternal to the system chassis. In the first L3 embodiment, there is nogateway IP interface or L3 FIB on any NM or VIOC and the system hardwaredoes not provide any L3 forwarding assists. That is, the externalgateway IP interface and L3 FIB are not aware of the fabric transportprocess and function conventionally to provide the Ethernet MACDA of thenext hop. In a second L3 embodiment, at least one gateway IP interfaceis implemented via a media port (physical port) or pseudo-port (virtualport) somewhere on at least one NM and an L3 FIB is implemented withineach NM having a gateway IP interface. In the second L3 embodiment,there is not a gateway IP interface or L3 FIB on any VIOC. The gatewayIP interface is only visible from inside the chassis if implemented on apseudo-port. The gateway IP interface is visible from inside and outsidethe chassis if implemented on a media port. Combinations of multiplegateway IP interfaces, some on media ports and others on pseudo ports,are envisioned. In a third L3 embodiment, a gateway IP interface isimplemented somewhere on at least one NM and for each VNIC, and an L3FIB is implemented within each NM and VIOC. Gateway IP interfaces and L3FIBs implemented within the chassis are fabric packet aware and assistL3 forwarding by providing the fabric destination address of the nexthop.

In the second and third L3 embodiments, L3 FIB management processesmaintain a master L3 FIB in the SCM and maintain coherency between allL3 FIBs in the chassis. When a non-master L3 FIB encounters adestination IP address that has no corresponding entry, the IP fabricpacket undergoing the forwarding decision is forwarded as an “exceptionpacket” to the controlplane process executing on the Primary SCM. Thecontrolplane process determines the proper fabric address for themissing entry, propagates a new entry to all of the L3 FIBs, andforwards the IP fabric packet to the destination IP (or at least one hopcloser) using the newly learned fabric address. (Fabric frames exist fora single cellified hop across the fabric between fabric source andfabric destination. In the above and the following it will be understoodthat when an IP fabric packet is “forwarded” via an indirection or hopvia an gateway IP interface or the Primary SCM, the IP fabric packet isbeing re-instantiated into a new fabric frame for each traverse acrossthe fabric.)

In accordance with the foregoing, depending upon embodiment and withinwhich module an IP packet is first processed, an IP fabric packet mayfirst undergo an indirection to an IP gateway interface, possibly on adifferent port or pseudo port on the same or a different module orexternal to the system. All transport is by conventional Ethernet framesoutside the chassis and by fabric frames within the chassis. Once at anIP gateway interface, the destination IP address of the originalEthernet frame is used to associatively access the L3 FIB and the lookupresult is used to forward the IP packet to the IP destination (or atleast one hop closer).

Those of ordinary skill in the art will understand that for IP packettransfers over the fabric, generally a gateway IP interface must beinvolved. In the following illustrated data exchanges, the paths aredrawn for scenarios that do not require additional indirection.Nevertheless, it will be understood that if an IP packet is received atan interface that is neither the IP destination address or a gateway IPinterface, then generally the corresponding data exchange path ismodified by interposing an intermediate hop to a gateway IP interface.Furthermore, when an IP packet is received at a gateway IP interface,either directly or as part of an indirection from a non-gateway IPinterface, in the relatively rare event that there is a miss in theassociated L3 FIB, the corresponding data exchange path is modified byinterposing an intermediate hop to the Primary SCM. As previouslyindicated, Primary SCM controlplane processing services the miss in themaster L3 FIB and updates the L3 FIBs throughout the chassis. Once themiss is serviced, the Primary SCM forwards the IP packet toward theoriginally intended destination. Thus, while not a frequent occurrence,for some IP fabric packets two intermediate hops are interposed in thedata exchange paths: a first intermediate hop to a gateway IP interfaceand a second intermediate hop to the Primary SCM.

In at least L3 forwarding, the classification functionality of the NMsfacilitates more sophisticated forwarding decisions, special datamanipulation, and other data treatments, to be optionally performed as afunction of additional attributes of the network data trafficencountered. In one particular example that will be examined in moredetail elsewhere herein, the fabric destination address for IP fabricpackets is at least in part determined by the recognition of particularservice requests (and the lack thereof) embedded in the data traffic.More specifically, the service request recognition takes the form ofrecognizing particular Transmission Control Protocol/Internet Protocol(TCP/IP) destination ports corresponding to particular applications. TheL2 and L3 FIBs are also updated dynamically, both in response to changesin the network configuration and optionally for dynamic performanceoptimization, such as to achieve load balancing among the processingresources of the system.

For the sake of clarity in the below initial expositions for each of thedata exchanges illustrated by FIGS. 1B and 2, the foregoing details ofthe transport process just described will be understood to apply, butwill not be repeated. It will also be understood that even though thedata exchanges are described from a flattened perspective that includesoperations by the clients, the modules, and the switch fabric, theunderlying above described fabric transport process (and the associatedmanagement of the L2 and L3 FIBs) remains transparent to the externalclients, external devices, and internal host software processes. Theseclients, devices and host software processes are only aware of packetsand messages (and not the fabric packets or fabric messages).

The data exchanges will be described in terms of more than one type ofpacket. References to packet transmission, packets originating from theclient, incoming packets, received packets, reassembled packets, orsimply packets, are references to Ethernet frames. It will be understoodthat all such Ethernet frames are transported across the fabric via theprocess of fabric packet encapsulation, cellification, switch fabrictraversal, and reassembly. References to augmented packets or cellifiedpackets are references to fabric packets. References to cells orcellified packets being forwarded refers to the providing offabric-addressed cells to the switch fabric for transfer by the switchfabric to the module coupled to the switch fabric egress port specifiedby the fabric address.

In each data exchange description, generic exchanges are purposefullynot explicitly characterized as being of the IP or non-IP type. It willbe understood that each of these data exchanges is generally equallyapplicable to the exchange of IP fabric packets or non-IP fabricpackets. If IP packets are being exchanged, then the forwarding isunderstood to be L3 forwarding. Otherwise, the forwarding is understoodto be L2 forwarding. Again for the sake of clarity in the followinginitial expositions, some details of the data exchanges, such as thehandling of multicast, are deferred to elsewhere herein.

Client-Server Data Exchange 115 includes packet transmission from Client102 via Ethernet Network 107 to NM 130A. Since the system may in part beproviding the functionality of an L2/L3 switch for any of many networksegments, packets received in close time proximity by NM 130A may be forany of multiple destinations both internal and external to the system.The incoming packets are classified, formed into fabric packets,subjected to a forwarding decision to determine a fabric address, andselectively provided as cells to Primary Switch Fabric Module 180A via afabric ingress port associated with NM-Fabric coupling 139A. Based inpart on the classification, NM 130A addresses the cells to PMM 150A, andmore specifically to SMP Portion P_(A) 152A, as a result of theforwarding decision identifying the fabric egress port associated withPMM-Fabric coupling 159A as the destination fabric addresses for thecells. Primary Switch Fabric Module 180A then transfers the cells to thefabric egress port associated with PMM-Fabric coupling 159A. SMP PortionP_(A) 152A receives the cells and reassembles them into received packetscorresponding to the packets originating from Client 102. The receivedpackets are formed directly in RAM 153A, typically via DMA write datatransfers. Return packets follow the flow in reverse, typicallybeginning with DMA read transfers from RAM 153A. Although Client-ServerData Exchange 115 has been described from the perspective of packets“originating” from Client 102 and return traffic flowing in reverse,this is only for illustrative purposes. The flow from Client 102 to SMPPortion P_(A) 152A is entirely independent of the flow in the otherdirection.

Not all packets received from Client 102 via Ethernet Network 107 aredestined to SMP Portion P_(A) 152A. For example, Client-Service DataExchange 117 illustrates cellified packets selectively forwarded by NM130A toward OLB 160A via NM-Fabric coupling 139A, Primary Switch FabricModule 180A, and OLB-Fabric coupling 169A. Based in part on theclassification, packets from Client 102 are determined to requiretransfer to OLB 160A (instead of other fabric clients, such as SMPPortion P_(A) 152A as in Client-Server Data Exchange 115). NM 130Aaddresses the corresponding cells to OLB 160A and executes a forwardingdecision identifying the fabric egress port associated with OLB-Fabriccoupling 169A as the fabric destination address for the cells. PrimarySwitch Fabric Module 180A then transfers the cells to the fabric egressport associated with OLB-Fabric coupling 169A. OLB 160A receives thecells and reassembles them into received packets directly into a RAMlocal to the OLB. Return packets follow the flow in reverse.

In one embodiment, messages are used to implement Fibre Channel storagetransactions. Storage-Server Data Exchange 116 includes establishing areliable end-to-end logical connection, directly reading message datafrom RAM 153A (included in SMP Portion P_(A) 152A), fragmenting (asrequired) the message data into fabric frames, and providingcorresponding cells addressed to FCM 120A via PMM-Fabric coupling 159A.As a result of a forwarding decision, the cell destination addressesspecify the fabric egress port associated with FCM-Fabric coupling 129A.For each fabric frame sent, the cells are transferred, received, andreassembled in a manner similar to that described for fabric packets inconjunction with Client-Service Data Exchange 117. The storagetransactions are provided via a storage network coupling to at least onestorage device of external Storage Network 106. If more than one storagenetwork and associated storage network coupling is associated with FCM120A, the particular storage network coupling is specified via a fabricsub-address portion of the cell destination address. Returning storagetransaction responses follow the flow in reverse.

Service Data Exchange 118 is similar to Client-Service Data Exchange117. Packet data is read from RAM 153A′ (included in SMP Portion P_(A)^(,) 152A′), and cells are forwarded to OLB 160A by a forwardingdecision specifying the fabric egress port associated with OLB-Fabriccoupling 169A as the cell destination addresses. The packets exchangedby Client-Server Data Exchange 115, and Client-Service Data Exchange117, and Service Data Exchange 118, are typically but not necessarily IPpackets.

In some embodiments, Data Exchanges 115-118 are overlapped or partiallyconcurrent with each other. For example, cells corresponding to aportion of Client-Server Data Exchange 115 traffic may be intermixedwith cells relating to Client-Service Data Exchange 117 traffic, as thecells from both data exchanges are coupled via NM-Fabric coupling 139Ato the fabric. However, each cell includes sufficient information in thecorresponding fabric destination address and other information tospecify the proper operation. For example, at NM-Fabric coupling 139A,cells of Client-Server Data Exchange 115 are forwarded to SMP PortionP_(A) 152A by a first forwarding decision specifying the fabric egressport associated with PMM-Fabric coupling 159A, while cells ofClient-Service Data Exchange 117 are forwarded to OLB 160A by a secondforwarding decision specifying the fabric egress port associated withOLB-Fabric coupling 169A. Similarly, cells from Client-Service DataExchange 117 and Service Data Exchange 118 may be intermixed onOLB-Fabric coupling 169A, because sub-port destination address and otherinformation in the cells enable proper processing. In one embodiment, aportion of the sub-port destination address is used to associate packetswith a respective input queue within the destination module.

In some embodiments, the termini of Data Exchanges are located in RAMthat is directly accessible by one or more processing elements. Forexample, Service Data Exchange 118 includes a first terminus in RAM153A′, and a second terminus in a RAM within OLB 160A. In typicalembodiments, packet data from the RAMs are read and written by DMA logicunits included in each of the respective modules. Conceptually, data isstreamed from a source RAM as packets, cellified and provided to thefabric, transferred to the egress port as specified by the cells,reassembled, and stored into a destination RAM in packet form. Theseoperations, in some embodiments, are fully overlapped, or pipelined, sothat data from a first cell of a packet may be stored into thedestination RAM while data from a following cell of the same sourcepacket is being read from the source RAM.

Packet and Process Data Flow

FIG. 2 illustrates various example embodiments of packet and processdata flow in an ES1 110A embodiment. A plurality of FCMs are illustratedby FCM 120A and FCM 120B, coupled to Primary Switch Fabric Module 180Avia FCM-Fabric coupling 129A and FCM-Fabric coupling 129B, respectively.A plurality of NMs are illustrated by NM 130A and NM 130B, coupled toPrimary Switch Fabric Module 180A via NM-Fabric coupling 139A andNM-Fabric coupling 139B, respectively. A plurality of PMMs areillustrated by PMM 150A and PMM 150B, coupled to Primary Switch FabricModule 180A by PMM-Fabric couplings 159A/159A′ and PMM-Fabric couplings159B/159B′, respectively. CSFI 170 is coupled to PMM 150A and PMM 150Bby CSFI-PMM coupling 179A and CSFI-PMM coupling 179B, respectively. Aplurality of OLBs are illustrated by OLB 160A and OLB 160B, coupled toPrimary Switch Fabric Module 180A by OLB-Fabric coupling 169A andOLB-Fabric coupling 169B. Note: the Redundant SIM and associatedcouplings are omitted from the figure for clarity.

It will be understood that each of the active FCMs and NMs of FIG. 2 aretypically, but not necessarily, coupled to external devices on externalnetworks as illustrated in FIGS. 1A and 1B. It remains the case that alltransport is by conventional Ethernet frames outside the chassis and byfabric frames within the chassis. Nevertheless, when such externaldevices or networks are involved, the termini of FCM-related andNM-related packet and message data exchanges may be considered from acertain perspective to extend to those external devices. However, evenwith coupled external devices, exchanges for at least some fabric framesrelated to system management and control will terminate within thevarious modules. Furthermore, in certain embodiments and scenarios,including scenarios with external devices, certain non-control dataexchanges terminate within the NMs. Specifically, for the case of fabricIP packets unicast to the IP gateway interface on a pseudo port withinan NM, the data exchange to the pseudo port terminates within the NM andis not visible externally.

As a first illustrative configuration scenario, PMM 150A is shownconfigured as two physical partitions, P₁ 201, and P₂ 202, while PMM150B is shown configured as a single physical partition P₃ 203. As asecond illustrative configuration scenario, mutually exclusive withrespect to the first configuration scenario, PMM 150A and PMM 150B areshown configured as a single unified physical partition P₄ 204.

FCM-PMM Data Exchange 210 is representative of data exchanged between astorage sub-system coupled to an FCM and a PMM, or more specifically aphysical partition of a PMM. As illustrated, this traffic is typicallystorage related messages between processes executing on P₃ 203 of PMM150B (including any of Application, Driver, or OS Processes) and anexternal storage sub-system (such as SAN 106 of FIG. 1B). In operation,bidirectional message information flows as cellified fabric frames viaFCM-Fabric coupling 129A, Primary Switch Fabric Module 180A, andPMM-Fabric coupling 159B. For example, a storage sub-system request isgenerated by a storage sub-system Driver process executing on P₃ 203.The request is formed as a storage sub-system message addressed to theexternal storage sub-system coupled to FCM 120A, and delivered ascellified fabric frames to Primary Switch Fabric Module 180A viaPMM-Fabric coupling 159B. Primary Switch Fabric Module 180A routes thecells to FCM-Fabric coupling 129A.

FCM-Fabric coupling 129A delivers the cellified fabric frames to FCM120A. In turn the cells of each fabric frame are reconstituted (orreconstructed) into the original storage sub-system message request,which is then sent to the storage sub-system attached to FCM 120A (suchas Fibre Channel Storage Network 106 of FIG. 1B, for example). Thestorage sub-system returns a response message, which is formed by FCM120A into one or more fabric messages addressed to P₃ 203. The fabricmessages are fragmented into fabric frames that are delivered as cellsto Primary Switch Fabric Module 180A via FCM-Fabric coupling 129A.Primary Switch Fabric Module 180A routes the cells via PMM-Fabriccoupling 159B to P₃ 203 of PMM 150B. P₃ 203 reconstitutes the cells intofabric frames, then reassembles and delivers the response message to thestorage sub-system Driver process executing on P₃ 203.

In various embodiments, FCM-PMM Data Exchange 210 may flow viaPMM-Fabric coupling 159B′ instead of 159B, or it may flow partially viaPMM-Fabric coupling 159B and partially via PMM-Fabric coupling 159B′.The operation is similar for these cases, as the fabric messages may beforwarded to P₃ 203 via 159B and 159B′ with no other change inoperation.

NM-OLB Data Exchange 211 is representative of data exchanged between anNM and a service process executing on an OLB. NM 130A receivesinformation, typically but not necessarily in IP packet form, from anexternal coupled client (such as Client 102 of FIG. 1B), and classifiesthe packets, in part to determine a subset of the packets to be sent toOLB 160B. Based in part on the classification, an appropriate subset ofthe information is formed into like-kind fabric packets including thedestination address of OLB 160B. An appropriate L2/L3 forwardingdecision is made and the fabric packets are then communicated as cellsto Primary Switch Fabric Module 180A via NM-Fabric coupling 139A.Primary Switch Fabric Module 180A forwards the cells toward OLB 160B.The cells are ultimately received via OLB-Fabric coupling 169B,reconstituted as packets, and provided directly to the service processexecuting on OLB 160B. The reverse path is used to transfer informationfrom the service process to the client coupled to NM 130A. Another pathmay also be used to transfer information from the service process toother destinations, such as an application process executing on a PMM.

In an example of an SSL service process executing on OLB 160B, NM 130Arecognizes a variety of SSL IP packet forms during classification,including HyperText Transfer Protocol Secure (HTTPS) as TCP/IPdestination port 443, Secure Simple Mail Transport Protocol (SSMTP) asTCP/IP destination port 465, and Secure Network News Transfer Protocol(SNNTP) as TCP/IP destination port 563. IP fabric packets are formedincluding the destination IP address of OLB 160B. An L3 forwardingdecision is made and the IP fabric packets are provided as cells to thefabric and forwarded toward OLB 160B. The SSL service process executingon OLB 160B, upon receiving the reconstituted IP packets, performs SSLservice functions such as context switching, state look-up, protocollayer demultiplexing, and decryption.

The SSL service process executing on OLB 160B produces result data basedin part on the packets received from the external client via NM 130A.The result data typically includes IP packets that may sent back to theexternal client via NM 130A (a handshake or acknowledgement, forexample) as illustrated by NM-OLB Data Exchange 211 or alternatelyaddressed to P₃ 203 (decrypted clear text, for example) as illustratedby PMM-OLB Data Exchange 216. In both cases fabric packets are providedas cells to Primary Switch Fabric Module 180A via OLB-Fabric coupling169B and forwarded accordingly.

In an example of an SLB service process executing on OLB 160B, NM 130Arecognizes TCP SYN packets during classification and forms an IP fabricpacket including the destination IP address of OLB 160B. An L3forwarding decision is made and the IP fabric packet is provided ascells to the fabric and forwarded toward OLB 160B. The SLB serviceprocess executing on OLB 160B, upon receiving a reconstituted packet,consults load information for the system, and assigns the request to arelatively unloaded physical partition of a PMM (such as one of P₁ 201,P₂ 202, and P₃ 203), establishing a new connection. The new connectionis recorded in the appropriate L3 FIBs, in order for NM 130A to properlyforward subsequent IP packets for the new connection to the assignedphysical partition, enabling information flow from NM 130A to theassigned physical partition without the need for indirection through OLB160B.

In one embodiment, SSL and SLB processing may be cascaded. For example,NM 130A forwards cellified encrypted IP packet information from anencrypted external client toward OLB 160B for SSL processing, ordecryption. OLB 160B in turn forwards cellified decrypted (clear text)IP packet information to itself, another OLB, or a PMM for subsequentSLB processing. After assignment of a physical partition relating to anew encrypted connection, cellified packets are then forwarded firstfrom NM 130A to OLB 160B for decryption, and then directly to theassigned physical partition.

In an example of an XML service executing on OLB 160B, the serviceprocess functions as an XML server. NM 130A identifies XML requests fromthe external client, and forwards each request, in the form of cellifiedIP packets, toward OLB 160B, where the XML service process analyzes therequest. Appropriate response information is produced and provided ascellified packets forwarded toward NM 130A.

While NM-OLB Data Exchange 211 illustrates data exchange between NM 130Aand OLB 160B, this is only an illustrative scenario. For example, duringclassification, NM 130A may examine a packet (typically but notnecessarily an IP packet) received from the client coupled to NM 130A todetermine an associated flow, and then selectively determine adestination OLB based on the determined flow (OLB 160A or OLB 160B, asappropriate). This provides a form of service processing load balancing.The destination OLB may also be determined based on the type of service(SLB, SSL, or XML), if a particular OLB includes hardware accelerationspecific to a service. For example, in an embodiment where OLB 160Aincludes an SSL hardware accelerator, while OLB 160B includes an XMLhardware accelerator, then IP packets requiring SSL processing aretypically directed toward OLB 160A, and IP packets requiring XMLprocessing are typically directed toward OLB 160B. Those of ordinaryskill in the art will recognize that destination OLB determination maybe performed based on combining service processing load balancing withselection based on hardware accelerator availability and location.

Service processing (such as SLB, SSL, and XML) is not restricted toOLBs, as PMMs and SCMs may also be configured to provide serviceprocessing. In these embodiments, NMs take the destination IP addressassigned to a physical partition of a PMM (such as P₁ 201, P₂ 202, or P₃203, for example) or an SCM (such as Primary SCM 140A, for example) andperform an L3 forwarding decision to provide a fabric destinationaddress in preparation for transit on the fabric as cells. The cells arethen forwarded toward the appropriate PMM or SCM where the serviceprocess is executing.

NM-NM Data Exchange 212 is representative of data exchanged between NMs.This traffic is exemplary of network traffic between a first externalclient and a second external client coupled respectively to a port of NM130A and a port of NM 130B, and wherein ES1 110A performs as a bridge,switch, or router. (Clients such as 102 and 103 of FIG. 1A arerepresentative of the external clients.) The low-level details of thedata exchange are substantially similar to NM-OLB Data Exchange 211. Aport of NM 130A receives information, typically in packet form, from thefirst external client (and potentially a plurality of other externalsources), and classifies the packets (which may be for a plurality ofdestinations), in part to determine a subset of the packets to be sentto the port of NM 130B. Based in part on the classification, anappropriate subset of the information is formed into fabric packetsdestination-addressed to the port of NM 130B. NM 130A makes a forwardingdecision that embeds a fabric address into the fabric packet, which isthen communicated as cells to Primary Switch Fabric Module 180A viaNM-Fabric coupling 139A. Primary Switch Fabric Module 180A forwards thecells toward NM 130B. After arriving at NM 130B the cells arereconstituted as packets, and sent to the second external client coupledto the port of NM 130B. The reverse path is used to transfer informationfrom the second client to the first client, and operates in a symmetricmanner.

Under some circumstances, such as multiple clients coupled to one NM viamultiple physical network couplings (media ports), an NM (such as NM130A) may forward data toward itself via the fabric. Operation in thisscenario is similar to NM-NM Data Exchange 212, except the packets areaddressed to NM 130A, instead of NM 130B. The multiple media ports aredistinguished via the sub-address portion of the fabric address.

NM-PMM Data Exchange 213 is representative of IP packets exchangedbetween an NM and a process (Application, Driver, or OS) executing on aPMM, typically under control of a higher-level protocol, such asTransmission Control Protocol (TCP) or User Datagram Protocol (UDP). Thedata exchange is substantially similar to NM-OLB Data Exchange 211. NM130B forms a portion of received information (based on classification)as IP packets addressed to P₃ 203. NM 130B executes a forwardingdecision on the destination IP address to obtain a fabric destinationaddress in preparation for providing a fabric packet as cells to PrimarySwitch Fabric Module 180A via NM-Fabric coupling 139B. Primary SwitchFabric Module 180A forwards the cells toward P₃ 203. Upon arrival viaPMM-Fabric coupling 159B (or alternatively PMM-Fabric coupling 159B′),the cells are reconstituted as IP packets by PMM 150B, and provided toP₃ 203. The process transfers information to NM 130B (and typically onto a client coupled to the NM) using the reverse path. A return IPfabric packet is formulated by the process, IP destination-addressed toNM 130B, a corresponding fabric address is obtained from a forwardingdecision, and the IP fabric packet is provided as cells to PrimarySwitch Fabric Module 180A for forwarding toward NM 130B.

NM-SCM Data Exchange 214 is representative of data exchanged between anNM (or a client coupled thereto) and a management, forwarding, or loadbalancing process executing on an SCM. The data exchange issubstantially similar to NM-OLB Data Exchange 211. Packets addressed toPrimary SCM 140A are formulated by either an external client coupled toNM 130B or (as an alternative example) by a control plane relatedprocess running on the Network Processor of NM 130B. NM 130B formscorresponding fabric packets and a forwarding decision is made todetermine the embedded fabric address. The fabric packets are thenprovided as cells to Primary Switch Fabric Module 180A via NM-Fabriccoupling 139B. Primary Switch Fabric Module 180A forwards the cellstoward Primary SCM 140A. Upon arrival at Primary SCM 140A via SCM-Fabriccoupling 149A, the cells are reassembled as packets by Primary SCM 140Aand provided to the management, controlplane, or load balancing process.Examples illustrating these processes are provided in the followingparagraphs. The management, controlplane, or load balancing processtransfers information back to NM 130B (or a client coupled thereto)using the reverse path. A management packet is addressed to NM 130B (orthe client coupled thereto), is formulated by a process executing on SCM140A, a corresponding fabric packet is formed, and a forwarding decisionis made to determine the embedded fabric address. The fabric packet isprovided as cells to Primary Switch Fabric Module 180A for forwardingtoward NM 130B. Upon arrival at NM 130B, the management packet isreconstructed. If addressed to NM 130B, the packet is consumed therein.If addressed to the external client, the reconstructed packet isprovided thereto.

In an example of a management process executing on Primary SCM 140A, amanagement client coupled externally to NM 130B (typically for remoteserver management, provisioning, configuration, or other relatedactivities) sends a management related packet via NM 130B with thedestination address of the management process executing on Primary SCM140A. Within NM 130B, the packet is classified and determined to be amanagement related packet. A forwarding decision is then made and acellified version of the management packet is forwarded toward themanagement process via Primary Switch Fabric Module 180A. Returninformation from the management process to the management client usesthe reverse path, by formulation (within SCM 140A) of packets having thedestination address of the management client coupled to NM 130B. Aforwarding decision is then made and a cellified version of the returninformation packets are forwarded toward the management client viaPrimary Switch Fabric Module 180A and NM 130B. Typically but notnecessarily, IP packets would be used for the exchange between themanagement client and process.

In an example of a controlplane process executing on Primary SCM 140A,in some embodiments and under some circumstances NM 130B classificationdetermines that the proper L2 forwarding for a received packet is notknown, and designates the received packet is an “exception packet”. Inone embodiment, NM 130B forwards a cellified version of the exceptionpacket to an L2 FIB management process executing on the Primary SCM viaPrimary Switch Fabric Module 180A. The L2 FIB management processexamines the exception packet, master L2 FIB, and other forwardingrelated information, to determine the proper fabric address for themissing L2 FIB entry. The updated forwarding information is thenrecorded in the master L2 FIB, in some embodiments, and propagated tothe ancillary L2 FIBs in order for NM 130B to properly forwardsubsequent packets having the same or similar classification. PrimarySCM 140A also provides a correct fabric address for the exception packetand emits an IP fabric packet equivalent to the exception packet (butaddressed to the updated fabric address) as corresponding cells toPrimary Switch Fabric Module 180A for forwarding to the interface atdestination IP address (or at least one hop closer). In thiscircumstance the fabric destination could be any of the elements coupledto the dataplane of Primary Switch Fabric Module 180A, including NM 130Bor Primary SCM 140A (this general data exchange is not illustrated inthe figure).

In an example of a load balancing process executing on Primary SCM 140A,operation is similar to the SLB service executing on an OLB, except theIP packets are destination IP addressed to Primary SCM 140A instead ofan OLB.

PMM-SCM Data Exchange 215 is representative of data exchanged between anApplication, Driver, or OS process executing on a physical partition ofa PMM and a management, controlplane, or load balancing processexecuting on an SCM. The data exchange is substantially similar to theexchanges described elsewhere herein. A PMM-to-SCM communication isformed as a packet addressed to Primary SCM 140A by a Driver process,for example, executing on P₃ 203. A fabric packet is formed and aforwarding decision is made to determine the embedded fabric address.The fabric packet is then provided as cells via PMM-Fabric coupling 159B(or 159B′), and forwarded via Primary Switch Fabric Module 180A towardPrimary SCM 140A. Upon arrival at Primary SCM 140A and subsequentreassembly, the reassembled packet is provided to the management,controlplane, or load balancing process. The reverse path is used forSCM-to-PMM communication, with the management, controlplane, or loadbalancing process formulating a packet addressed to P₃ 203, forcommunication to the Driver process.

In an example of the load balancing process executing on Primary SCM140A, the communication includes server load information relating to PMM150B. PMM-SCM Data Exchange 215 is also representative of a variety ofpaths between an SCM and all other elements coupled to the fabricdataplane (such as FCMs, NMs, OLBs, and other PMMs), to updateforwarding information maintained in each of the elements. For eachelement requiring a forwarding information update, the controlplaneprocess executing on Primary SCM 140A formulates one or more packets toinclude the updated forwarding information and addresses the packet(s)to the appropriate fabric destination. The packets are provided as cellsto the fabric and the fabric forwards the cells according to the fabricdestination. In another embodiment the fabric destination includes amulticast destination, and the cellified packets are delivered to aplurality of destinations by the fabric.

PMM-OLB Data Exchange 216 is representative of data exchanged between aprocess (Application, Driver, or OS) executing on a physical partitionof a PMM and a service process executing on an OLB. The data exchange issubstantially similar to PMM-SCM Data Exchange 215, except that OLB 160Btakes the place of Primary SCM 140A, and data is coupled via OLB-Fabriccoupling 169B instead of SCM-Fabric coupling 149A.

Data exchanges between processes executing on different physicalpartitions are communicated on the fabric (PMM-PMM-Fabric Data Exchange217, for example). Data exchanges between processes executing within thesame physical partition are communicated by coherent shared memory andcoherent cache memory transactions (PMM-Internal Data Exchange 218, forexample). When multiple PMMs are configured as a single physicalpartition, coherent shared memory and coherent cache memory transactionstravel between the PMMs of the partitions via CSFI 170 (PMM-PMM-CSFIData Exchange 219, for example).

PMM-PMM-Fabric Data Exchange 217 is representative of data exchangedbetween a first process and a second process executing on differentphysical partitions, i.e. message-passing InterProcess Communication(IPC). The two processes may be any combination of Application, Driver,or OS processes. The data exchange is substantially similar to PMM-SCMData Exchange 215, except P₁ 201 takes the place of Primary SCM 140A,and data is coupled via PMM-Fabric coupling 159A′ instead of SCM-Fabriccoupling 149A. Another example of this type of communication would bebetween P₁ 201 and P₂ 202, (via PMM-Fabric coupling 159A′ and PMM-Fabriccoupling 159A) even though these two physical partitions are on the samePMM.

PMM-Internal Data Exchange 218 is representative of data exchangedbetween two processes executing on the same physical partition, and thephysical partition resides entirely within a single PMM. A sourceprocess, executing on a first compute element of P₃ 203, writes to ashared memory location, and a sink process, executing on a secondcompute element of P₃ 203, reads the shared memory modified by thewrite. Communication is provided by links internal to PMM 150Bsupporting coherent shared memory and coherent cache memory.

PMM-PMM-CSFI Data Exchange 219 is representative of data exchangedbetween two processes executing on the same physical partition, thephysical partition spans more than one PMM, and the two processesexecute on different PMMs. An example of this physical partitionconfiguration is illustrated as P₄ 204, where P₄ 204 includes all of thecompute elements of PMM 150A and PMM 150B. Coherent shared memory andcoherent cache memory transactions are used to exchange data, as inPMM-Internal Data Exchange 218. However, the transactions arecommunicated via CSFI 170, instead of links internal to the PMMs.

Data exchanges may also occur between processes executing on physicalpartitions distributed across multiple PMMs via a combination of pathssimilar to PMM-Internal Data Exchange 218 and PMM-PMM-CSFI Data Exchange219. That is, particular coherent memory traffic (for both shared memoryand cache memory) may travel via both CSFI 170 and via links internal tothe PMMs.

Data exchanges involving an NM (such as 211, 212, 213, and 214)typically include Tag processing. Specifically, during ingressprocessing on an NM, incoming packets from a first client coupled to theNM are classified, producing a condensed representation of certaindetails of the incoming packet, typically by analyzing the header of theincoming packet. A portion of the classification result is representedby a Tag, and typically a portion of the Tag, referred to as the egressTag, is included in a header of the fabric packet produced by the NM inresponse to the incoming packet. The egress Tag may specify selectedpacket processing operations to be performed by the NM during egressprocessing, thus modifying the packet header, data, or both, beforereceipt by a second client. Egress packet processing may be performed inresponse to the corresponding Tag produced during ingress processing (inthe NM that did the ingress processing on the packet) or in response toa Tag ‘manufactured’ by a service process on an OLB or an Application,Driver, or OS process executing on a PMM. In one embodiment egressprocessing is specified directly by the Tag, and in another embodimentegress processing is determined indirectly by the Tag (via a tablelook-up, for example).

As an example, during NM-OLB Data Exchange 211, in the case of an SSLservice process, the egress Tag provided may include informationexamined by the SSL process in order to perform any combination of SSLprocessing related context switching, SSL related per context statelook-up, and early protocol layer demultiplexing.

As another example, during NM-SCM Data Exchange 214, in the case of arouting process, the exception packet delivered to the routing processmay include an egress Tag providing exception information to determine aparticular Quality of Service (QoS) for the associated routing protocol.The routing process examines the exception information of the egress Tagto determine the particular route processing queue to insert theexception packet into.

In one embodiment, Primary Switch Fabric Module 180A provides for only asingle transport of cells at a time between any pairing of ingress andegress ports. In another embodiment, Primary Switch Fabric Module 180Aprovides for a plurality of simultaneous transports of cells betweenmultiple pairings of fabric ingress and egress ports. This simultaneoustransport may be by parallel communication paths available in thefabric, by interleaving cells from different transports in time on asingle communication path, or any combination of these and othertechniques. Those of ordinary skill in the art will recognize that thedetails of Primary Switch Fabric Module 180A operation affect only theavailable bandwidth and latency provided by the fabric, not details ofdata exchanges as exemplified by FCM-PMM Data Exchange 210, NM-OLB DataExchange 211, and so forth. In one embodiment, Primary Switch FabricModule 180A includes sufficient parallel resources to providesubstantially simultaneous communication for all of the data exchangesillustrated in the figure.

Packet Transmission and Reception

FIG. 3A illustrates Fabric Communication 300A, conceptually showingselected aspects of an embodiment of packet transmission and receptionin an ES embodiment, used in FCM-PMM Data Exchange 210 and other similardata exchanges described elsewhere herein. Fabric client elementscoupled to Primary Switch Fabric Module 180A include PMM 150A, OLB 160A,NM 130A, FCM 120A, and Primary SCM 140A. Each coupled client includesRAM, shown respectively as PMM RAM 350, OLB RAM 360, NM RAM 330, FCM RAM320, and SCM RAM 340. Each RAM in turn includes a packet memory image,shown respectively as Packet Memory Image PKT_(PMM) 351, Packet MemoryImage PKT_(OLB) 361, Packet Memory Image PKT_(NM) 331, Packet MemoryImage PKT_(FCM) 321, and Packet Memory Image PKT_(SCM) 341. A VIOC isincluded in each of PMM 150A, OLB 160A, FCM 120A, and Primary SCM 140A,illustrated as VIOC 301.5, VIOC 301.6, VIOC 301.2, and VIOC 301.4,respectively. The VIOCs are shown conceptually coupled to correspondingpacket images as dashed arrows 359, 369, 329, and 349, respectively. TheVIOCs provide an interface to the fabric via PMM-Fabric coupling 159A,OLB-Fabric coupling 169A, FCM-Fabric coupling 129A, and SCM-Fabriccoupling 149A, respectively.

NM 130A includes a Traffic Manager (TM 302), also known as a Buffer andTraffic Manager (BTM) instead of a VIOC. The TM is shown conceptuallycoupled to Packet Memory Image PKT_(NM) 331 via dashed arrow 339. TM 302provides an interface for NM-Fabric coupling 139A.

Data is exchanged between fabric clients (modules on the fabric) byprocedures of packet transmission, routing (as cells) on the fabric, andpacket reception. Arrow 315 conceptually shows the direction of flow forpacket transmission to the fabric, also referred to as ingress to thefabric, while arrow 316 conceptually shows the direction of flow forpacket reception from the fabric, also referred to as egress from thefabric. Conceptually, packet transmission begins at the source fabricclient by reading a packet image from a source RAM and providing thepacket as cells for transmission via the fabric. The fabric routes thecells to the appropriate destination fabric client. Packet receptionconceptually begins at the fabric edge of the destination fabric client,where the cells are received from the fabric and reassembled into acorresponding packet (including information from the packet image asread from the source RAM) and written into a destination RAM in thedestination fabric client.

Each of TM 302 and the VIOCs (301.5, 301.6, 301.2, and 301.4) comprisevarious logic blocks, including a fabric interface communication unit(also known as a packet-cell converter) for performing the functionsrelating to packet transmission and packet reception via cells on thefabric. The fabric communication operation of all fabric clients (PMM150A, OLB 160A, NM 130A, FCM 120A, and Primary SCM 140A) issubstantially similar, but for clarity is described in a context of dataexchanged between PMM 150A and NM 130A (such as NM-PMM Data Exchange213, for example).

For a packet transmission operation, the fabric interface communicationunits read a packet image from a RAM included in a fabric client (suchas Packet Memory Image PKT_(PMM) 351 included in PMM RAM 350). Thepacket image includes a header and packet body data, illustrated asHeader 311 and Packet Body 312 respectively. The fabric interfacecommunication unit (included in VIOC 301.5 in this example) conceptuallysegments the packet into a plurality of cells of equal length,illustrated as Cell C₁ 313.1′ through Cell C_(M-1) 313.(M-1)′. The finalCell C_(M) 313.M′ is typically a different length than the other cellsas packets are not restricted to integer multiples of cell sizes.Although illustrated as contiguous in RAM, the packet body data mayinstead be scattered in various non-contiguous buffers in RAM, accordingto various embodiments.

Each of the cells are encapsulated with headers, illustrated as CellHeader h₁ 314.1, corresponding to Cell C₁ 313.1, and Cell Header h_(M)314.M corresponding to Cell C_(M) 313.M. The cell headers for each ofthe cells segmented from a given packet are determined in part from thepacket header, as shown conceptually by arrow 310.1 and arrow 310.Mflowing from Header 311 to Cell Header h₁ 314.1 and to Cell Header h_(M)314.M respectively. Each of the resultant encapsulated cells isprovided, in order, to the fabric for routing to the destination.Segmenting the packet into cells and encapsulating the cells is alsoreferred to as “cellification”.

Header 311 includes a packet destination address, and VIOC 301.1determines a cell destination address in part from the destinationaddress of the packet header in addition to routing tables and stateinformation available to the VIOC. The cell destination address, alsoknown as a fabric destination or egress port address, is included ineach of the cell headers (Cell Header h₁ 314.1 through Cell Header h_(M)314.M).

This technique enables a process executing on a fabric client totransparently address a packet to another fabric client using a logicaladdress for the addressed client. The resolution of the packet addressto a fabric egress port address corresponds to resolving the logicaladdress to a physical address, i.e. a specific port of the switch thatthe addressed client is coupled to.

The reverse direction receive path operates in a complementary,conceptually symmetric, inverse manner The segmented cells are routed bythe fabric, in order, to the fabric port specified by the celldestination address. The fabric interface communication unit included inthe destination fabric client receives the cells, processes the headers,and reconstitutes (or reconstructs) the cells into a packet image inRAM, resulting in a packet image substantially similar to the packetimage originally provided by the transmitting fabric client. Continuingwith the example, if the destination address of Packet Memory ImagePKT_(PMM) 351 resolves to NM 130A, then the cells are routed toNM-Fabric coupling 139A by Primary Switch Fabric Module 180A. TM 302receives the cells via NM-Fabric coupling 139A, assembles them back intoa packet, and stores the resultant image as Packet Memory Image PKT_(NM)331 in NM RAM 330.

Those of ordinary skill in the art will recognize that packettransmission and reception procedures are not limited to complete packetimages in RAM. For example, on an NM, packet information flowing to thefabric may be provided, in some embodiments, directly from a networkinterface included on the NM, without intermediate storage in RAM.Similarly, packet information flowing from the fabric may, in someembodiments, be provided directly to the network interface withoutintermediate storage in RAM. The same techniques may be used on an FCMwith respect to information flowing to and from the storage interface.Those of ordinary skill in the art will also recognize that thesans-header intermediate cells, Cell C₁ 313.1′ through Cell C_(M)313.M′, are only conceptual in nature as some embodiments implementcellification without copying packet data. Instead, packet data isaccessed in-situ in cell-sized chunks and encapsulation performedon-the-fly.

The fabric interface communication units included in TMs and VIOCsfurther include logic adapted to allocate and manage bandwidth andpriority for various flows as identified by any combination ofclassification information, Tag, and a sub-port portion of a fabricegress port address. This enables provisioning of bandwidth and settingof priorities for transport according to operational requirements.

In one embodiment, the particular priority at which transport isperformed is selectively determined by examination of the sub-portportion of the fabric egress port address. For example, NM 130A may beconfigured with a high-priority queue and a low-priority queue, havingcorresponding high-priority and low-priority sub-port addresses. Withrespect to NM-PMM Data Exchange 213, for example, a portion of the dataexchange may be performed via the low priority queue and another portionperformed via the high-priority queue. A process desiring selectiveaccess to the high-priority queue and low-priority queue addressespackets accordingly, providing a corresponding high-priority packetdestination address to high-priority packets and a correspondinglow-priority packet destination address to low-priority packets. Duringtransmission to the fabric, the high-priority packet address and thelow-priority packet address are resolved by the appropriate VIOC on PMM150B to a corresponding high-priority fabric egress port address and acorresponding low-priority egress port address. The high-priority egressport address and the low-priority egress port address include a fabricport number sub-portion that is identical for the two egress portaddresses, since both packets are destined to the same pluggable module.However, the sub-port portion is different to distinguish between highand low priorities.

Upon receipt in the NM of high-priority cells and low-priority cells(corresponding to cells from packets addressed to the high-priorityqueue and the low-priority queue, respectively), the TM on NM 130Aexamines the sub-port portion of the fabric egress port addressesprovided with each cell, and selectively identifies packets asassociated with the high-priority queue or the low-priority queue asappropriate.

In another embodiment, the sub-port portion may also include a bandwidthallocation portion to identify one of a plurality of bandwidthallocations to associate with the packet assembled from the cell. Stillother embodiments provide for combining priority and bandwidthallocation dependent processing according to the sub-port portion of thefabric egress port address. Those of ordinary skill in the art willrecognize that these techniques are not limited to communication betweenNMs and PMMs as in the example, but may be used between all modulesoperating as fabric clients (such as FCMs, SCMs, and OLBs). FCMs, forexample, may provide for allocation of bandwidth to various coupledstorage devices or networks via the sub-port mechanism.

In one embodiment, the fabric interface communication units of TMs andVIOCs provide hardware support for a reliable message protocol inaddition to packet communication. State machines implement aconnection-oriented procedure including establishing a connection via aconnection request and a corresponding acknowledgement, sending andreceiving one or more messages using the established connection, andterminating the connection after it is no longer needed. Delivery ofmessage content is guaranteed, using a limited number of retries,otherwise an error is returned to the sender. In operation, messageimages are constructed similar to packet images, with an indicatorincluded in the message image identifying the image as a message insteadof a packet. The message image includes a message header, similar informat to a packet header, and message body data, similar to packet bodydata. The message body data is communicated in the same manner as packetbody data. The message header includes a message destination similar informat to a packet destination address. The message destination addressis resolved into a cell destination address for inclusion in the cellsduring cellification, similar to the resolution of a packet destinationaddress.

FIG. 3B illustrates Prioritized Fabric Communication 300B, conceptuallyshowing selected aspects of an embodiment of packet and cell prioritizedtransmission in an ES embodiment, focusing on transports originatingfrom a VIOC. VIOCs 301.5 and 301.6, along with TM 302, are coupled toPrimary Switch Fabric Module 180A, via couplings 159A, 169A, and 139A,respectively. A VIOC typically is closely associated with 16 groups offour transmit queues each, providing a total of 64 transmit queues. Herein this initial illustrative embodiment the transmit queues areconceptualized as existing within the VIOC. In a later discussedillustrative embodiment, the transmit queues physically reside in sharedportions of the host memory, although their state is managed within theVIOC and portions are buffered within the VIOC.

A subset of three transmit queues are shown conceptually in VIOC 301.6,as Q₁ 309.1, Q₂ 309.2, and Q₃ 309.3. Each transmit queue is configurableas operating according to a specified priority or according to aspecified bandwidth. For example, Q₁ 309.1 may be configured to operateat a strictly higher priority than Q₂ 309.2 and Q₃ 309.3, or the queuesmay be configured to operate in a round-robin priority with respect toeach other. As another example, Q₁ 309.1 may be configured to operate attwice the bandwidth of Q₂ 309.2 and Q₃ 309.3. As another example, Q₁309.1 may be configured for a first maximum bandwidth and a firstminimum bandwidth, Q₂ 309.2 may be configured for a second maximum and asecond minimum bandwidth, and Q₃ 309.3 may be configured for thirdmaximum and minimum bandwidths. Those of ordinary skill in the art willrecognize that many other priority and bandwidth schemes are possible.

In addition to transmit queues, VIOCs typically implement virtual outputqueues (VOQs) to prevent head of line blocking, in order to maximize thebandwidth of transmission to the fabric. In an illustrative embodimentdiscussed herein below, the VOQs are implemented as pointer managedbuffers within an egress shared memory internal to the VIOC. A subset ofVOQs in VIOC 301.6 are illustrated as VOQ₁ 308.1 and VOQ₂ 308.2, one foreach of the two illustrated destinations (VIOC 301.5 and TM 302). TheVOQs are processed according to configurable priority algorithms,including a straight (or strict) priority algorithm, a straightround-robin algorithm (without weights), a weighted round-robinalgorithm, and a weighted round-robin algorithm with configurableweights, according to embodiment.

In operation, a transmit queue selection is made according to theconfigured priority and bandwidth. Data is then made available from theselected queue accordingly, and provided to the fabric for transfer tothe destination according to the virtual output queue associated withthe destination. These procedures repeat as long as any of the queuesare not empty. In the example, one of Q₁ 309.1, Q₂ 309.2, and Q₃ 309.3is selected, and then examined to determine the next packet (or message)to transmit. For illustrative purposes, Q₁ 309.1 is configured as thehighest priority, Q₂ 309.2 is the next highest priority, and Q₃ 309.3 isconfigured as the lowest priority.

A first selection and subsequent transmission, shown conceptually asPacket Transmission Path 317.1, is made from Q₁ 309.1, as it isconfigured as the highest priority, and includes at least one packetready for transmission. Data is read according to Q₁ 309.1, anddetermined to be destined for the fabric egress port associated withPMM-Fabric coupling 159A. Data is transferred to Primary Switch FabricModule 180A under the control of VOQ₁ 308.1, and further transferred toPMM-Fabric coupling 159A.

Subsequently, a second selection and transmission, shown conceptually asPacket Transmission Path 317.2, is made from Q₂ 309.2, as it isconfigured as the next highest priority, it includes at least one packetready for transmission, and Q₁ 309.1 is empty. Data is read according toQ₂ 309.2, determined to be destined for PMM-Fabric coupling 159A,provided to Primary Switch Fabric Module 180A under the control of VOQ₁308.1, and transferred to PMM-Fabric coupling 159A.

Subsequently, a third selection and transmission, shown conceptually asPacket Transmission Path 317.3, is made from Q₃ 309.3, as it isconfigured as the lowest priority, it is not empty, and Q₁ 309.1 and Q₂309.2 are empty. Data is read according to the selected transmit queue(Q₃ 309.3) as in the previous two scenarios, but the destination isdetermined to be the fabric egress port associated with NM-Fabriccoupling 139A, and therefore data is provided to the fabric under thecontrol of VOQ₂ 308.2.

Although the three selections and transmissions corresponding to PacketTransmission Paths 317.1, 317.2, and 317.3 have been described asoccurring strictly sequentially, transmission of data from differingvirtual output queues may instead be interleaved on the fabric. Forexample, transmission of data from VOQ₁ 308.1 (such as PacketTransmission Paths 317.1 or 317.2) may overlap in time with thetransmission of data from VOQ₂ 308.2 (such as Packet Transmission Path317.3). In this circumstance, cells from the overlapping transmissionsare wholly or partially interleaved on the fabric.

In addition to prioritized selection among the transmit queues, theswitch fabric also typically provides for prioritized transport. Eachcell may specify a priority, and in one embodiment there are fourpriority levels available. The cell priority is developed from anycombination of various parameters, including packet size, packet type,packet class of service, packet quality of service, transmit queuepriority, and other packet header information. As shown in the figure,Cell Transmission Path 318.1 provides for transmission of cells fromVIOC 301.6 to VIOC 301.5, and Cell Transmission Path 318.2 provides fortransmission of cells from VIOC 301.6 to TM 302. Each of Paths 318.1 and318.2 may transfer cells according to any of the four priorities. Forexample, cells corresponding to Packet Transmission Path 317.1 may betransferred at the highest priority, while cells corresponding to PacketTransmission Path 317.2 may be transferred at a lower priority.

Those of ordinary skill in the art will recognize that these describedscenarios are examples only, as entries in the transmit queues may bedestined for any of the egress ports of the fabric, and therefore any ofthe corresponding VOQs. In addition, dynamic transmit queue priorities(such as round-robin) and bandwidth allocation associated constraintsand processing may result in data from various transmit queues beingintermingled in various VOQs, although all of the data for a givenpacket will necessarily be present in the same VOQ, since the packet isdestined for only a single fabric egress port. Furthermore, fabrictransport priorities may vary amongst entries in the VOQs, such that theswitch fabric traffic typically appears intermixed and complicated.

Pluggable Modules

FIGS. 4A-4E illustrate various embodiments of pluggable modules includedin various ES embodiments. The modules share many similarcharacteristics. For example, each of the modules includes a fabricinterface communication unit included in a TM or a VIOC. Each of themodules typically includes one or more computation and memory elements.Couplings between elements of the modules typically operate in the sameor substantially similar fashion. These similarities are illustrated bycommon element presentation and identification, as follows.

RAM elements are shown with identifiers prefixed with 411, and theseelements are typically Dyanimc Random Access Memories (DRAMs) organizedas Dual Inline Memory Modules (DIMMs) in some embodiments. CPU elementsare shown with identifiers prefixed with 410, and these elements aretypically Opteron processors. VIOC identifiers are prefixed with 301.Elements representing combined Ternary Content Addressable Memory (TCAM)and Static Random Access Memory (SRAM) identifiers are prefixed with403. BMC elements are prefixed with 402. FCI elements are prefixed with413, and the associated optional coupling identifiers are prefixed with414. HyperTransport (HT) channel couplings are shown with identifiersprefixed with 460.

Those of ordinary skill in the art will recognize that while theaforementioned elements shown with common prefix identifiers are closelyrelated to each other in operation and function, they are not identical,and may differ in various characteristics. Differences may include size,organization, bandwidth, capacity, or speed, according to embodiment.Such differences have no effect on the overall operation of theassociated pluggable module.

FIG. 4A illustrates SIM Detail 400A, including selected aspects of anembodiment of a SIM configured as a pluggable module including an SCMand an associated SFM. It will be understood that the discussion of FIG.4A is made with respect to the capabilities and topology of the primarySIM and primary fabric, but the discussion equally describes theredundant topology and latent capabilities of the secondary SIM andsecondary fabric. As discussed elsewhere herein, the secondary fabricremains dormant with respect to non-control dataplane functionally aslong as the primary fabric operates properly. Primary SCM 140A includescompute and associated memory elements CPU 410.4L/RAM 411.4L coupled toCPU 410.4R/RAM 411.4R via HT coupling 460.4L. VIOC 301.4 is coupled toCPU 410.4R via HT coupling 460.R. VIOC 301.4 is in communication withTCAM/SRAM 403.4. and provides a fabric interface for SCM-Fabric coupling149A. Management I/O 412 is coupled to CPU 410.4L via HT coupling 460.4Mand provides an interface to the intra-chassis BMCs via coupling 452.Primary SCM 140A also includes BMC 402.4 coupled to VIOC 301.4 andManagement I/O 412. As discussed in more detail later herein, MassStorage 412A is coupled to Management I/O 412 via coupling 453 andprovides local mass storage.

Primary Switch Fabric Module 180A includes Primary SFM Dataplane (SFDP)404 having a plurality of fabric ports with respective fabric portaddresses. The fabric ports are coupled to the various system modulesvia SCM-Fabric coupling 149A, FCM-Fabric coupling 129A, NM-Fabriccoupling 139A, PMM-Fabric coupling 159A, and OLB-Fabric coupling 169A.Each module in the system may be coupled to one or more of the fabricports and at least some of the foregoing illustrated fabric couplingsrepresent more than one full-duplex fabric coupling to the PrimarySwitch Fabric Module 180A. For example, in one embodiment, there maybeup to two PMM modules and each PMM module has two full-duplex fabriccouplings. Thus PMM-Fabric coupling 159A may be representative of fourfull-duplex fabric couplings to four respective fabric ports, eachhaving a respective fabric port address. Each module or portion thereofhaving its own fabric coupling to a fabric port is addressable via thecorresponding fabric port address. Primary Switch Fabric Module 180Aalso includes Primary Switch Fabric Scheduler 401 coupled to PrimarySFDP 404.

In operation, SFDP 404, under the direction of Switch Fabric Scheduler401, routes data as cells provided to a fabric ingress port to a fabricegress port, according to a cell destination address, as describedelsewhere herein. Each of dataplane couplings 149A, 129A, 139A, 159A,and 169A couples with a respective fabric ingress port and a respectivefabric egress port.

Primary SCM 140A executes any combination of management, controlplane,and load balancing processes using compute and memory resources providedby CPU 410.4L/RAM 411.4L and CPU 410.4R/RAM 411.4R. The CPUs operate asa single SMP complex, communicating shared memory coherency and cachememory coherency transactions via HT coupling 460.4L.

VIOC 301.4 operates as an intelligent I/O device responding to commandsfrom the CPUs, typically originating from a Driver process. A Driverprocess executing on one of the CPUs forms a packet image in one of theRAMs, including specifying a destination address for the packet, andthen notifies the VIOC that a new packet is available for transmission.In response, the VIOC fabric interface communication transmit unitdirectly accesses the packet image from RAM via an included transmitDirect Memory Access (DMA) unit. The VIOC examines the packet header andidentifies the packet destination address. The transmission of packetsas cells proceeds without direct assistance from any of the processesexecuting on the CPUs. The packet address and other associatedinformation are referenced in accessing forwarding and state informationmaintained in TCAM/SRAM 403.4 to determine the corresponding fabricegress port address and other related information for inclusion inheaders of cells provided to the fabric to transmit the packet as cells.

VIOC 301.4 also operates as an intelligent I/O device in the reversedirection, in a conceptually symmetric fashion. Cells are received fromthe fabric and reassembled as packets by the VIOC fabric interfacecommunication receive unit. In one embodiment the packet data ispartially reassembled directly into a packet image stored in one of theRAMs via an included receive DMA unit. The reception of packets as cellsproceeds without direct assistance from any of the processes executingon the CPUs. The VIOC notifies one or more of the CPUs that new packetdata is available, and subsequently a process, typically a Driverprocess, accesses the packet image provided in RAM and processes itaccordingly.

The management process (or processes) executing on the CPUs of PrimarySCM 140A communicate management and configuration control informationvia Management I/O 412 between Primary SCM 140A and other modules viacoupling 452 coupled to BMCs included in PMM 150A, NM 130A, FCM 120A,OLB 160A, and Primary SCM 140A (local BMC 402.4). This communication istypically via a dedicated management Ethernet network, and isconsequently out-of-band with respect to Primary Switch Fabric Module180A. BMC 402.4 provides baseboard management functions, communicatingwith Management I/O 412 and VIOC 301.4. The processes executing on theCPUs of Primary SCM 140A collect selected management information fromall BMCs in the server and in response to the collected information andprovisioning commands received from elsewhere, provide management andconfiguration commands to the BMCs. Management I/O 412 also communicatesconfiguration and control information via coupling 451 betweenmanagement and controlplane processes executing on the CPUs and SwitchFabric Scheduler 401. This provides, for example, for static or dynamicconfiguration of the SCMs, one as the Primary SCM and the other as theRedundant SCM.

In selected embodiments, a mass storage device (such as Mass Storage412A) or storage network interface is available locally to provide bootimages, management information, provisioning information, or log filestorage. Mass Storage 412A may include any combination of mass storagedevice types including Flash memory, Magnetic Disk memory, and OpticalDisk memory. The mass storage devices may be coupled via any combinationof storage interface types including but not limited to PC Card, CompactFlash, Multi-Media Card, Memory Stick, Smart Card, Secure Digital,Universal Serial Bus (USB), FireWire, SCSI (Small Computer SystemInterface), IDE (Integrated Device Electronics), EIDE (Enhanced IDE) andvariations and successors thereof. In other embodiments, the local massstorage is omitted, and this data is accessed from mass storage devicesor networks remotely via FCMs 120 or NMs 130.

FIG. 4B illustrates PMM Detail 400B, including selected aspects of anembodiment of a PMM configured as a pluggable module. The PMM isarranged as a pair of identical sections, Half-PMM 430 and Half-PMM430′. Each section includes two CPU/RAM elements coupled to each otherby HT links, a VIOC/TCAM/SRAM element interfacing to a fabric coupling,and an optional FCI. The coupling of these elements is substantiallysimilar to corresponding elements of Primary SCM 140A, except thatManagement I/O 412 is omitted. The two Half-PMMs share BMC 402.5.

The two Half-PMMs are coupled to each other by a pair of HT links (HTcoupling 460.5X and HT coupling 460.5Y). One of the CPUs of each halfalso provides an HT interface for coupling to another PMM (such as PMM150B of FIG. 2) via CSFI-PMM coupling 179A and CSFI-PMM coupling 179A′.As discussed in more detail below, in one embodiment these couplings arecoupled directly to another identically configured PMM, and in otherembodiments these couplings are coupled indirectly to another PMM viaCSFI 170 (with variations illustrated in FIG. 1A and FIG. 2). Sharedmemory coherency and cache memory coherency transactions arecommunicated over the HT couplings internal to the PMM (460.5L, 460.5X,460.5L′, and 460.5Y) and over HT couplings external to the PMM (179A,and 179A′).

The HT couplings communicating shared memory coherency and cache memorycoherency transactions and CSFI 170 are programmatically configurable toprovide for physical partitioning of the CPU/RAM elements of PMMs. ThePMM is configured as a single 4-way physical partition by programmingthe internal HT links (460.5L, 460.5X, 460.5L′, and 460.5Y) for coherentoperation, and programming the external HT links (179A, and 179A′) for“isolated” operation (i.e. links 179A and 179A′ are disabled). Inanother embodiment, isolating a PMM for configuration as a single 4-wayphysical partition (or as two 2-way physical partitions) is performed byprogrammatically configuring CSFI 170 (of FIG. 1A) to isolate the PMMfrom other PMMs.

The PMM is configured as a pair of identical 2-way physical partitions(Half-PMM 430 and Half-PMM 430′) by programmatically configuring aportion of the internal HT links (460.5L, and 460.5L′) for coherentoperation, and another portion of the internal HT links (460.5X, and460.5Y) for isolated operation. The external HT links (179A, and 179A′)or CSFI 170 are also programmed for isolated operation.

A plurality of PMMs are configured as a single unified 8-way physicalpartition by programmatically configuring all of the internal andexternal HT links of all of the PMMs (and also CSFI 170, depending onthe embodiment) for coherent operation. Those of ordinary skill in theart will recognize that an arbitrary number and arrangement of physicalpartitions may be configured from PMMs 150, as limited only by theavailable resources, using the techniques described.

In operation, each PMM is programmatically partitioned according toprovisioning information. Physical partitions can be established thathave one-half of a PMM (2-way), a single PMM (4-way), or two PMMs(8-way). It will be understood that the number of SMP-ways per half of aPMM is merely illustrative and not limiting as is the configurabletopology for aggregation of SMP-ways. Application, Driver, and OSprocesses are executed on the resultant physical partitions. Eachresultant physical partition always includes at least one VIOC. The VIOCprovides for communication between the executing processes and otherclients of the fabric via packet images in memory, operating asdescribed elsewhere herein.

In selected embodiments, one or both of optional FCIs 413.5 and FCI413.5′ are included, to access boot images or related information, viacouplings 414.5 and 414.5′ and FCIs 413.5 and 413.5′, from either alocal mass storage device or via a mass storage network. In otherembodiments, the optional FCIs are omitted, and this data is accessedvia the fabric from mass storage devices or networks via fabric-coupledFCMs 120 or NMs 130.

As suggested by the CSFI variations illustrated by FIGS. 1A and 2, thoseof ordinary skill in the art will recognize that CSFI 170 may be whollyor partially implemented on the SIM, on the PMM, on a separate module,or any combination of SIM, PMM, and separate module, or any otherconvenient location. The coherent switch functionality may beimplemented in conjunction with the HT links on the PMM, or implementedindependently of these functions without substantially modifying theoperation. In some embodiments, CSFI 170 is limited to interconnectoperating in conjunction with coherency and switching logic implementedinternal to the CPU elements included on the PMMs. In other embodiments,CSFI 170 includes some portion of coherency and switching logicoperating in conjunction with coherency and switching logic included onthe PMMs.

FIG. 4C illustrates NM Detail 400C, including selected aspects of anembodiment of a Network Module (NM) configured as a pluggable module. NM130A includes media interface hardware specific to a particular type ofnetwork coupling (Interfaces 420 and 419 for couplings 426 and 427,respectively), coupled to network processing elements adapted for packetprocessing, including Packet Classification and Editor (PCE 417) andassociated CAM 418, coupled in turn to Traffic Manager (TM 302). TM 302is in communication with RAM 416, and provides a fabric interface forNM-Fabric coupling 139A. Control Processor (CP) 429 is coupled to PCE417 and TM 302. NM 130A also includes BMC 402.3, coupled to CP 429, PCE417 and TM 302. The BMC provides an interface for coupling 452. Whilethe illustrated embodiment shows CP 429 coupled to Management I/O 412indirectly via BMC 402.3, in alternate embodiments the CP is coupled tothe Management I/O via a coupling shared with the BMC, and in furtheralternate embodiments the CP is coupled to the Management I/O via adedicated (i.e. not shared) coupling.

In operation, information (typically in the form of packets)communicated between a network device (typically external to the ES1)coupled to coupling 426 is processed at a low-level and in aninterface-specific manner by Interface 420 (the operation of coupling427 and Interface 419 is substantially similar). Packets received fromthe network device are provided to PCE 417 for classification and Tagdetermination, as described elsewhere herein. The packet data and Tagare stored in RAM 416, and provided to the fabric as cells by TM 302 viaNM-Fabric coupling 139A. In the reverse direction, cells are reassembledby TM 302 as received from the fabric via NM-Fabric coupling 139A, andthe resultant packets are stored in RAM 416. PCE 417 reads the storedpacket data, and dynamically modifies it according to any associated Taginformation, providing the result to Interface 420 for transmission tothe network device via coupling 426.

TM 302 operates as a fabric interface communication unit, and includes afabric interface communication transmit unit that directly accesses thepacket image from RAM via an included DMA unit. The TM examines thepacket header and identifies the packet destination address. The packetaddress and other associated information are referenced in accessingrouting and state information maintained in one or more of CAM 418 andRAM 416. The resultant fabric egress port address and other relatedinformation are included in headers of cells provided to the fabric totransmit the packet as cells.

TM 302 also includes a fabric interface communication receive unit thatoperates in a conceptually symmetric fashion. Cells are received fromthe fabric and reassembled as packets stored into RAM 416 via anincluded DMA unit. The TM notifies the PCE as new packet data becomesavailable for editing and transport to Interface 420.

CP 429 manages various HW resources on the NM, including PCE 417 and TM302, and respective lookup elements CAM 418 and RAM 416. The CP receivesmanagement information via coupling 452 (either indirectly via the BMCor directly via a Management I/O coupling, according to embodiment) andprograms lookup, forwarding, and data structure information included inCAM 418 (such as associatively searched information) and RAM 416(such astrie table information).

FIG. 4D illustrates FCM Detail 400D, including selected aspects of anembodiment of an FCM configured as a pluggable module. FCM 120A includesFibre Channel compatible couplings 428.1A through 428.4B, coupled inpairs to Fibre Channel interface Processors (FCPs 423.1-423.4). The FCPsare in turn coupled to a compute and storage element including InputOutput Processor (IOP 421) and associated RAM 422, coupled in turn toVIOC 301.2. The VIOC provides a fabric interface for FCM-Fabric coupling129A. FCM 120A also includes BMC 402.2 coupled to VIOC 301.2 andproviding an interface for coupling 452.

In operation, information communicated between Fibre Channel compatibledevices or networks coupled to couplings 428.1A through 428.4B isprocessed in a low-level manner by FCPs 423.1-423.4. Informationreceived from external storage devices is typically stored as packets inRAM 422. After optional processing by IOP 421, packet data istransmitted as cells to the fabric by the fabric interface communicationtransmit unit of VIOC 301.2 via FCM-Fabric coupling 129A (as describedelsewhere herein). In the reverse direction, cells are reassembled byVIOC 301.2 as received from the fabric via FCM-Fabric coupling 129A, andthe resultant packets are stored in RAM 422. In one embodiment, IOP 421reads the stored data, providing the end result to FCPs 423.1-423.4 fortransmission to the coupled device or network. In an alternateembodiment, FCPs 423.1-423.4 access the data directly via DMA.

FIG. 4E illustrates OLB Detail 400E, including selected aspects of anembodiment of an OLB configured as a pluggable module. OLB 160A issimilar in many respects to Primary SCM 140A, and includes compute andassociated memory elements CPU 410.6L/RAM 411.6L coupled to CPU410.6R/RAM 411.6R via HT coupling 460.6L. VIOC 301.6 is coupled to CPU410.6R via HT coupling 460.6R. VIOC 301.6 is in communication withTCAM/SRAM 403.6 and provides a fabric interface for OLB-Fabric coupling169A. PCI sub-module 425 and HT sub-module 424 are optionally includedin various combinations and configurations in several embodiments toprovide additional service-specific computational capabilities asservice acceleration modules. OLB 160A also includes BMC 402.6 coupledto VIOC 301.6 and providing an interface for coupling 452.

PCI sub-module 425 includes a PCI interface for interfacing PCI-adapterbased devices to HT coupling 460.6R. HT sub-module 424 includes an HTinterface for coupling to CPU 410.6R via coupling 460.6X. Variousembodiments of PCI sub-modules and HT-sub-modules further include anynumber and combination of service-specific hardware acceleratorsaccording to implementation, such as an SLB hardware accelerator, an SSLhardware accelerator, and an XML hardware accelerator.

In operation, OLB 160A executes any combination of service processes(relating to SLB, SSL, or XML, for example) using compute and memoryresources provided by CPU 410.6L/RAM 411.6L and CPU 410.6R/RAM 411.6R.The CPUs operate as a single SMP complex, communicating shared memorycoherency and cache memory coherency transactions via HT coupling460.6L. The VIOC provides for communication between the executingprocesses and other clients of the fabric via packet images in memory,operating as described elsewhere herein. Service processes executing onembodiments including any combination of PCI sub-module 425 and HTsub-module 424 access elements of the sub-modules in order to accelerateprocessing related to the service processes.

Software Layers

FIG. 5A illustrates Application SW Layering 500A, including selectedaspects of embodiments of SW layers for executing on applicationprocessor resources, such as CPUs included on PMMs, of an ES embodiment.The layers are represented in a first context for execution on P₃ 203,and in a second context for execution on P₁ 201. As described elsewhereherein, P₃ 203 and P₁ 201 correspond to distinct physical partitionsconfigured from one or more PMMs.

Although Application SW Layering 500A is illustrated as representativeof a collection of code images, in some contexts it may be useful toconsider it as conceptually representative of processes, or groups ofprocesses associated with each of the illustrated elements. For example,Hypervisor1 510 represents a code image of a specific Hypervisor, but itmay also be considered conceptually representative of all processes andrelated execution threads associated with executing any portion of theHypervisor code image. In typical embodiments, a plurality of concurrentexecution streams co-exists and cooperates while executing portions ofthe code image. Similarly, OS1/Drivers 1 507, Appl 501, and so forth,may be considered representative of groups of respective processesassociated with each of the respective SW elements.

Illustrated at the highest (most fundamental and privileged) SW layerlevel is a Hypervisor layer, as shown by Hypervisor1 510 and Hypervisor2520. Hypervisors typically provide a software environment for executinga plurality of OS instances in an apparently concurrent manner viatimesharing on a shared hardware resource, such as P₃ 203 or P₁ 201, asillustrated in the figure. At the middle SW layer level is an OS layer.As shown, Hypervisor1 510 provides two logical partitions, one forOS1/Drivers 1 507, and another for OS2/Drivers 2 508. Hypervisor2 520provides a single logical partition for OS3/Drivers 3 509.

Illustrated within the OS layer are Drivers, including VIOC and VNICDrivers. A VIOC Driver provides an interface between management andcontrolplane processes and VIOCs. VIOC Drivers include VIOC Driver 1 511in OS1/Drivers 1 507, VIOC Driver 2 512 in OS2/Drivers 2 508, and VIOCDriver 3 513 in OS3/Drivers 3 509. VIOC Drivers, in some embodiments,are customized according to OS environment, such that VIOC Driver 1 511,VIOC Driver 2 512, and VIOC Driver 3 513 may be distinct if OS1/Drivers1 507, OS2/Drivers 2 508, and OS3/Drivers 3 509 or associatedenvironments are distinct. An OS layer may include one or more VIOCDrivers, depending on embodiment.

A VNIC Driver provides an interface between processes (executing onapplication processor resources, for example) and communicationresources as provided by VNICs (implemented by VIOCs, for example). Insome embodiments, a VNIC Driver is conceptually similar to a modifiedEthernet Driver. VNIC Drivers include VNIC Driver 1 514 and VNIC Driver2 515 in OS1/Drivers 1 507, VNIC Driver 3 516 and VNIC Driver 4 517 inOS2/Drivers 2 508, and VNIC Driver 5 518 and VNIC Driver 6 519 inOS3/Drivers 3 509. VNIC Drivers, in some embodiments, are customizedaccording to OS environment, such that VNIC Driver 1 514 and VNIC Driver3 516 may be distinct if OS1/Drivers 1 507 and OS2/Drivers 2 508 orassociated environments are distinct. In some embodiments, VNIC driversare further customized according to OS requirements or contexts, suchthat VNIC drivers within the same OS are distinct (VNIC Driver 1 514being distinct with respect to VNIC Driver 2 515, for example). An OSlayer may include one or more VNIC Drivers, each having uniquefunctions, parameters, or customizations, depending on embodiment.

The lowest SW layer level, the Application layer, is provided by the OSsfor executing Applications. OS1/Drivers 1 507 hosts a plurality ofApplications as shown by App1-App3 501-503. Similarly, OS2/Drivers 2 508hosts two applications, App4 504, and App5 505. OS3/Drivers 3 509 hostsa single application, App6 506.

Execution of SW at the different layers typically results in a pluralityof processes or execution streams, corresponding to program execution ofvarious portions or sub-portions of code from the illustrated SW layers.For example, execution of each of Hypervisor1 510, OS1/Drivers 1 507,and Appl 501 may result in a plurality of concurrently runningprocesses. One example of a process spawned from OS1/Drivers 1 507 is aDevice Driver process, for example a Device Driver process correspondingto execution of the modified Ethernet Driver described elsewhere herein.

In typical embodiments, VIOC Device Drivers are associated with VIOCmanagement and control, and VNIC Device Drivers are associated with VNICmanagement and control. According to various embodiments, OS1/Drivers 1507, OS2/Drivers 2 508, and OS3/Drivers 3 509 include variouscombinations of VIOC and VNIC Drivers. VIOC Drivers, VNIC Drivers, andassociated functions may be wholly or partially shared and combinedaccording to embodiment.

Those of ordinary skill in the art will recognize that the illustratedSW layering is only on example embodiment. Other embodiments may includemore layers (such as Application sub-layers) or fewer layers (such asdedicated physical partitions requiring no Hypervisor layer). There isalso no restriction as to the number and arrangement of Hypervisors,OSs, Drivers, and Applications, other than restrictions imposed by thefinite resources in an embodiment.

FIG. 5B illustrates Management SW Layering 500B, including selectedaspects of SW layers for executing on management processor resources,such as processor resources included on SCMs (Primary SCM 140A, forexample), OLBs (OLB 160A, for example), and PMMs (PMM 150A, forexample), according to various ES system embodiments. Generallyexecution of these SW layers results in various system control andsystem operational processes such as management, controlplane, and loadbalancing processes. As described elsewhere herein, the system controland management processes program various configuration and lookup stateinformation to implement provisioning, switching, and routing functionsin the EF architecture. Similar to Application SW Layering 500A,Management SW Layering 500B represents a collection of code images, andeach element may be usefully considered as representative of one or moreprocesses executing portions of each respective element.

Enterprise Manager 530 supports multi-chassis management, complexprovisioning, interfaces to client GUIs, and generally operates at arelatively high level of abstraction, as does CLI 532. Platform Manager531 generally performs in-chassis (or single-chassis) managementoperations and tends to manipulate system objects directly at arelatively low level of abstraction. Several SW modules operate in closecooperation with the Platform Manager, including Chassis Manager (CM)533, Query Engine 534, Repository Manager 535, VIOC Manager 536,Interface Manager 537, L2 Forwarding DataBase (FDB) Manager 538, VLANManager 539, and Other Management Code 540.

CLI 532 generally provides some combination of the CLI proper andrelated services to support the interface. CM 533 discovers and manageschassis resources. Query Engine 534 processes queries relating topersistent state managed by Repository Manager 535. VIOC Manager 536generally provides an interface between the system control andmanagement processes and VIOCs in a system. Interface Manager 537generally provides an interface between the system control andmanagement processes and NMs in a system. L2 FDB Manager 538 provides L2forwarding information management by maintaining one or more FDBs. TheL2 FDB Manager further manages dissemination of information related toportions of the FDB throughout the system as needed (such as updatingthe forwarding and state information maintained in TCAM/SRAM elementscoupled to VIOCs). VLAN Manager 539 generally provides system-widemanagement functions relating to provisioning VLANs and maintaining VLANrelated information, such as associations between VNICs, VLANs, and NMports. Typically a Logical InterFace identifier (LIF) is allocated perport per VLAN, identifying a “connection” to the VLAN. Other ManagementCode 540 generally provides other management, controlplane, and loadbalancing functions. The platform manager and the aforementioned closelycooperating SW modules are described in more detail elsewhere herein.

FIG. 5C illustrates BMC SW Layering 500C, including selected aspects ofSW layers for executing on module-level configuration and managementprocessor resources, such as BMCs (BMC 402.4 of FIG. 4A, for example),according to various ES system embodiments. Module BMC SW 550 supportsmodule-level operations, typically via interfaces with HW components onthe module the BMC is included on. The Module BMC SW generally functionsat a relatively low level of abstraction. Similar to Application SWLayering 500A and Management SW Layering 500B, BMC SW Layering 500Crepresents a collection of code images, and each element may be usefullyconsidered as representative of one or more processes executing portionsof each respective element.

In some embodiments, optional IPMI Client 551 provides an interface toIPMI services (typically part of Platform Manager 531) and in someembodiments serves to export low-level platform services to variouselements of the Management SW. Event Agent 552 monitors module-levelinformation (such as sensors and board insertion detection logic) torecognize changes in status and configuration of the module. The EventAgent then communicates these changes as events delivered to variouselements of the Management SW (such as CM 533). The Selected BMC EventDetails section, included elsewhere herein, provides further details onBMC events. Command Agent 553 receives BMC commands from variouselements of the Management SW (such as CM 533) and sequences andforwards the commands The Command Agent communicates results of commandexecution as events via functions provided by the Event Agent. TheSelected BMC Command Details section, included elsewhere herein,provides further details on BMC commands

VNIC Overview and Queuing Operation

As previously described, VNICs provide each processing element withaccess via a modified Ethernet Driver to other system resourcesconnected to the fabric. For example, each VNIC, in conjunction withtransport via the fabric and external communication via an NM, providescapabilities similar to that of a conventional NIC, made available toprocesses by way of a driver functionally similar to a conventionalEthernet driver. In the general case, the accessible system resourcesinclude networking interfaces provided by NMs, storage interfacesprovided by FCMs, and computing capabilities provided by SCMs, PMMs, andOLBs. In some embodiments, VNICs are implemented by VIOCs included inmodules such as PMMs, OLBs, FCMs, and SCMs, thereby providing processingelements on such modules with access to VNIC capabilities.

VNIC operation generally provides for communication of data directlybetween processes executing on a Local Processor and the fabric viaLocal Processor Memory. The Local Processor Memory is typicallyaccessible by the Local Processor and, for example, a VIOC implementingVNIC functionality. Conceptually, a VNIC provides transmit and receivequeues for use by processes executing on a Local Processor forcommunication of data (as packets or messages) to and from the LocalProcessor Memory.

As VNICs (like conventional NICs) are bidirectional, VNICs also provideaccess to each processing element from other system resources connectedto the fabric. For example, each VNIC on an OLB provides a separateportal to execution resources provided by the OLB. A first VNIC on theOLB may be allocated to and accessed by processes executing on a firstprovisioned server, while a second VNIC on the same OLB may be used by asecond provisioned server. As another example, each VNIC on an FCMprovides a separate path to storage resources enabled by the FCM, andeach of the separate paths may be accessed by distinct provisionedservers.

FIG. 6A illustrates selected aspects of a logical view of an embodimentof a plurality of VNICs. According to one embodiment, VIOC 301implements 16 identical VNICs. In the figure only two of the VNICs areshown (for clairty), VNIC #1 600.1 and VNIC #16 600.16. Each VNIC, suchas VNIC #1 600.1, includes programmable identification informationillustrated as Address Block 601.1, VNIC configuration registersillustrated as VNIC Configuration Block 618.1, and packet and messagedata communication interfaces illustrated as I/O Block 605.1.

Address Block 601.1 includes Fabric Address 602.1, for specifying thesource fabric address of the VNIC, and MAC Address 603.1, defining theMAC address associated with the VNIC. In some embodiments, a firstportion of Fabric Address 602.1 is common to some or all of the VNICs ofa VOIC, and corresponds to the physical fabric address of the VIOC. Asecond portion of Fabric Address 602.1, also known as the fabricsub-address, is unique to each VNIC. Address Block 601.1 optionallyincludes, according to embodiment, Public Internet Protocol (Public IP)Address 604.1, for specifying the IP address associated with the VNIC,to enable selected L3 processing.

Address Block 601.1 also includes a Virtual Local Area Network (VLAN)Identifier (VLANid 617.1), for use according to embodiment to map adestination address according to VLAN information, or as a tag toidentify the VNIC with respect to a VLAN for selected L3 processing, orboth. In some embodiments, a separate L3 VLAN identifier (in addition toVLAN Identifier 617.1) may be provided for use with selected L3 VLANoperations. Examples of VLAN processing include formulating a packet orcell header including a VLAN tag, and filtering incoming traffic withrespect to a VLAN. In various embodiments, programming of VLANIdentifier 617.1 further enables implementation of fabric-port-based,MAC address-based, IP address-based, and general L3 type VLAN functions.

VNIC Configuration Block 618.1 includes VNIC Enable 618.1 a, forenabling (and disabling) the corresponding VNIC, and priority andbandwidth configuration registers. The priority configuration registersinclude Priority Scheme Selection 618.1 b and Priority Weights 618.1 c,for specifying priority processing related information, such as priorityscheme selection and weights, respectively. The bandwidth configurationregisters include Bandwidth Minimum 618.1 d and Bandwidth Maximum 618.1e, for specifying bandwidth allocation and control configurations, suchas minimum and maximum bandwidth allocations, respectively, for thecorresponding VNIC.

I/O Block 605.1 includes separate collections of queues for packets andmessages. Each collection includes transmit, receive, and completionqueues (the completion queues are also known as receive completionqueues). The packet and message queues are organized by “context”. Eachcontext includes a transmit queue, a receive queue, and either acompletion queue or a pointer to a completion queue. In a typical usagescenario, the transmit, receive, and completion queues of a context areassociated with a particular protocol connection or a particularmultiplexed set of protocol connections. Each context is established bysoftware running on the Local Processors. In certain embodiments, whileeach context has a respective pair of dedicated transmit and receivequeues, multiple contexts are associated with a common completion queue.This is detailed further below.

A packet (or message) context may be used for IP traffic, interprocesscommunication (directly or over IP), or other similar communications.When accessed via physical buffer addresses, packet (or message)contexts are typically used directly by OS and Hypervisor processes, andtypically used indirectly (via system calls, for example) by applicationprocesses. When accessed via virtual buffer addresses, packet (ormessage) contexts are typically usable directly by applicationprocesses, in addition to direct use by OS and Hypervisor processes.

A single packet context may be used to implement multiple connectionsvia SW, while a single message context typically implements a singleconnection managed (at least in part) by HW. Message contexts may beused by RDMA operations with fewer SW operations than similarfunctionality implemented with packet contexts. In some embodiments,message contexts are typically directly accessible via applicationprocesses.

Each context has particular state associated with it, organized within aContext State Block (CSB), which identifies the context's transmit,receive, and completion queues. The CSBs are maintained in variousembodiments by any combination of hypervisor, OS, and Driver processesproviding control information for the VNIC.

The queues contain descriptors that are organized within circularbuffers in contiguous memory and thus are also known as descriptorrings. Each enqueued descriptor describes various aspects (detailedherein below) of the packets or messages being transmitted and received.In particular, the packet transmit and receive descriptors correspond tothe raw data buffers in the Local Processor Memory where packet data isrespectively read and written by the VIOC. A common scenario is forthese descriptors to have been prepared by processes of the LocalProcessors (such as a Driver).

Packet Contexts 606.1 provides four packet CSBs (also referred to aspacket contexts) of identical capability, two of which are illustratedin the figure (Packet Context Block #1 606.1.1 and Packet Context Block#4 606.1.4). As shown, each packet context includes a transmit queue,such as Packet Transmit Queue #1 607.1.1 and Packet Transmit Queue #4607.1.4., and a receive queue pointer, such as Packet Receive QueuePointer #1 608.1.1 and Packet Receive Queue Pointer #4 608.1.4.

Each packet receive queue pointer identifies one of 16 identical sharedpacket receive queues, as illustrated by dashed-arrow 619 r pointingtoward Packet Receive Queues 616 r. For clarity, only two of the 16packet receive queues are illustrated in the figure, specifically PacketReceive Queue #1 616 r.1 and Packet Receive Queue #16 616 r.16. Thepacket receive queue pointers enable arbitrary sharing of packet receivequeues among packet contexts, including sharing among packet contexts inmultiple distinct VNICs.

In alternate embodiments, packet context receive queues are not sharedamong VNICs, but are dedicated per VNIC as packet context transmitqueues are. In these alternate embodiments, 608.1.1 . . . 608.1.4operate directly as the packet receive queues for a given VNIC, andPacket Receive Queues 616 r (of FIG. 6A) is not provided.

Also included in each packet context is a completion queue pointer, suchas Packet Complete Queue Pointer #1 609.1.1 and Packet Complete QueuePointer #4 609.1.4. Each packet completion queue pointer identifies oneof 16 identical shared packet completion queues, as illustrated bydashed-arrow 619 c pointing toward Packet Completion Queues 616 c. Forclarity, only two of the 16 packet completion queues are illustrated inthe figure, specifically Packet Completion Queue #1 616 c.1 and PacketCompletion Queue #16 616 c.16. Similar to the packet receive queuepointers, the packet completion queue pointers enable arbitrary sharingof packet completion queues among packet contexts, including sharingamong packet contexts in multiple distinct VNICs.

The packet transmit queues of a VNIC (such as Packet Transmit Queue #1607.1.1, for example), also known as transmit rings, are used tocommunicate transmit packet availability and location in memory. Thetransmit queues include a plurality of transmit descriptors, each ofwhich refer to a buffer in memory having a complete or partial packetimage for transmission. The descriptor includes the address of thebuffer (in Local Processor Memory), the buffer size, a packet stateindicator, a valid indicator, a done indicator, and other relatedinformation. The packet state indicator describes the buffer informationas associated with the start, the middle, or the end of a packet.Assertion of the valid indicator specifies that the descriptor refers topacket image data ready for transmission. Deassertion indicatesotherwise: that no data is ready, the descriptor is invalid, or someother related condition. The valid indicator allows a VNICimplementation (such as a VIOC) to poll (or scan) the transmit queuesfor valid descriptors to discover packet data ready for transmissionwithout requiring any further information or stimulus from the processesexecuting on the Local Processor. The processes may also interrupt theVIOC by accessing a Doorbell location in the VIOC memory-mapped I/Oaddress space to indicate new or modified descriptors in a transmitqueue, corresponding to additional packet data ready for transmission. Aplurality of Doorbell locations are typically provided per VNIC. In someembodiments, packet transmit queues and message contexts of all VNICsare allocated distinct doorbells.

The packet receive queues of a VNIC (such as those pointed to by PacketReceive Queue Pointer #1 608.1.1, for example), also known as receiverings, are used to communicate receive packet data locations in memory.The receive queues include a plurality of receive descriptors, each ofwhich refers to a buffer in memory for reception of a complete orpartial packet image. The descriptor includes the address of the buffer(in Local Processor Memory), the buffer size, a valid indicator, andother related information. The valid indicator specifies that the bufferthe descriptor refers to is ready to receive packet image data, enablinga VNIC implementation (such as a VIOC) to determine receive bufferavailability without direct involvement of processes executing on theLocal Processor.

The shared packet completion queues (Packet Completion Queue #1 616 c.1,for example) are used to communicate completion information, includingreceive packet data availability and status. The completion queuesinclude a plurality of entries, each of which includes a packet statusindicator and other related information. The packet status indicatoridentifies buffer data as corresponding to the start, middle, or end ofa packet. When a receive buffer is filled, corresponding to consumptionof an associated receive descriptor, an entry is created in one of thecompletion queues. The completion queue data structure and relatedprocessing further enable a VNIC implementation (such as a VIOC) toprovide packet data to processes executing on Local Processors withlittle direct involvement of the processes. In some embodiments, theingress processing (e.g., packet reassembly from cells) performed by theVIOC/VNIC frees up resources for other tasks, and may also simplifyimplementation of other portions of the system.

In the illustrated embodiment, Message Contexts 610.1 provides up to atotal of 4K−4 (i.e., 2 to the 12^(th) power, minus 4, or 4092) messageCSBs (also referred to as message contexts) per VNIC. Each messagecontext has identical capability, and two are illustrated in the figure(Message Context Block #1 610.1.1 and Message Context Block #N 610.1.N).In other embodiments, (not illustrated), the message contexts of the 16VNICs are shared, for a total of 64K−16 (i.e., 2 to the 16^(th) power,minus 16, or 65,520) message contexts available collectively to all ofthe VNICs. As shown, each message context includes a transmit queue,such as Message Transmit Queue #1 611.1.1 and Message Transmit Queue #N611.1.N, and a receive queue, such as Message Receive Queue #1 612.1.1and Message Receive Queue #N 612.1.N. Also included in each messagecontext is a completion queue, such as Message Completion Queue #1613.1.1 and Message Completion Queue #N 613.1.N. The message transmit,receive, and completion queue data structures are similar to thosedefined for packet processing. The message data structures specifymessage location and availability for transmission, for determiningbuffer location and availability for reception, and for directlyproviding message data and completion status to processes executing onLocal Processors.

Messages are processed via an additional level of indirection not usedfor packet processing. Message Lists 615.1 includes two linked lists ofmessages to be processed (Message List #1 615.1.1 and Message List #2615.1.2). Each of the lists includes an active entry pointing to (orselecting) one of the message contexts, as illustrated by dashed-ellipse614.1 and associated dashed-arrows pointing to message contexts inMessage Contexts 610.1. In embodiments with 4K−4 message contexts perVNIC the active entries point to message contexts associated with theVNIC, and in embodiments with 64K−16 shared message contexts, the activeentries point to any of the shared message contexts. Each of theselected message contexts in turn includes transmit, receive, andcompletion queues, as illustrated.

Transmit and receive packet and message buffer addresses may be providedas physical addresses or virtual addresses subsequently translated by aVNIC implementation (such as a VIOC), depending on embodiment andconfiguration. In some embodiments and configurations, address typevaries according to queue, and may also vary according to otherconfiguration information.

In typical implementations, VNICs share resources amongst each other andbetween queues within each respective VNIC. Shared transmit resourcesinclude access to the fabric (based on destination, for example) andeffective bandwidth to the fabric (allocated between VNICs and queuesincluded in VNICs, for example). Shared receive resources include inputqueuing (or enqueuing) bandwidth from the fabric (based on acategorization included in the received data, for example) and dequeuingbandwidth from input queues to Local Processor Memory (allocated betweenVNICs and queues included in VNICs, for example).

Egress Path VNIC/Queue Operation

Sharing of transmit resources is managed by three scheduling policies.These are the transmit-descriptor-fetch scheduling policy, the VOQscheduling policy, and the subsequent-transmit-data-read schedulingpolicy. From a high-level perspective, the transmit-descriptor-fetchscheduling policy decides which transmit tasks the VIOC will do next.More specifically, the transmit-descriptor-fetch scheduling policy,described in more detail below in conjunction with FIG. 6B, determinesthe next transmit-descriptor to be fetched. (An initial data read isalso performed in conjunction with each transmit descriptor fetch.) Eachtransmit descriptor describes a transmit buffer in the local processormemory that holds one or more packets awaiting transport to theiraddressed destinations. The transmit descriptor to be next fetched isthe descriptor identified by the next descriptor pointer of a transmitqueue selected by the transmit-descriptor-fetch scheduling policy fromthe candidate pool of all VNIC transmit queues. The selection is basedin part on a prioritization among the VNIC transmit queues, in a mannerthat is configurable in part. The selection is also based in part on anapproximate fabric bandwidth allocation among the VNICs.

The VOQ scheduling policy, described in more detail below in conjunctionwith FIG. 6C, determines the next cell to transmit to the fabric. Thecell to be next transmitted to the fabric is the cell at the head of theVOQ selected by the VOQ scheduling policy from the candidate pool of allVOQs. The selection is based in part on a prioritization among the VOQs,in a manner that is configurable in part.

The subsequent-transmit-data-read scheduling policy determines the nexttransmit data to read (for all reads required to retire a transmitdescriptor made after the first data read). The transmit data to be nextread is the data (generally a cache-line in memory) identified by thenext data unit prefetch pointer of a transmit queue packet buffer (intransmit shared memory) selected by the subsequent-transmit-data-readscheduling policy from the candidate pool of all transmit queue packetbuffers awaiting to do transmit data reads.

Note that the solid arrows drawn in FIGS. 6B through 6E do not representdata flows (at least not required ones). Taking an analogy from sports,each of the solid-arrow diagrams is very similar to a “tournamentbracket” (also known as a tournament chart), wherein a pool ofcompetitors is reduced by successive stages of competition to arrive atan overall winner. In terms of this sports analogy, the transmit queuesrepresented at the start (on the left for transmit, on the right forreceive) “compete” in accordance with rules that may differ at eachstage to be chosen as the queue for which an action (different in eachfigure) is next performed.

In the following scheduling discussions, it will be understood thatalthough the description may refer to queue selections in each ofmultiple stages (“prioritization levels”), and that subsequent to thescheduling selection data is generally transferred, that neverthelesseach selection described is a logical abstraction that generally doesnot necessitate any data movement corresponding to any of: the queues,identifiers (or pointers) representing the queues, descriptors pointedto by the queues, or data associated with the descriptors. Furthermore,evaluation in each of the discrete stages described is also a logicalabstraction that need not be physically implemented in order to realizethe overall result. While in some embodiments the selection logic couldimplement pass gate or other multiplexing logic to pass transmit queueidentifiers (or other related data items) along circuit topographiesthat are fashioned after the tournament bracket topologies illustrated,this is not at all essential. Those of ordinary skill in the art willunderstand that each scheduling policy of FIGS. 6B through 6E isreducible to logic equations that can be implemented in manyfunctionally equivalent ways, including but not limited to: pass gates,multiplexers, AND/OR-gating, memory or programmable-logic arrays,micro-programming, and combinations thereof. Furthermore, only the finalresult of the scheduling process need be actually realized. That is,certain implementation approaches and optimizations may not actuallyimplement or expose the intermediate prioritization level results.

FIG. 6B illustrates selected aspects of a logical view of an embodimentof VNIC transmit-descriptor-fetch scheduling. For clarity, only thetransmit queue functions of two of the 16 VNICs are illustrated (VNIC #1600.1 and VNIC #16 600.16). The figure represents operations related toselecting a transmit queue from among all the transmit queues. The nextdescriptor pointer of the selected transmit queue in turn identifies thenext transmit descriptor to fetch, according to various prioritytechniques. This determines the relative processing order of packet andmessage buffers described by the transmit descriptors, and therebyapproximates and manages a per-VNIC effective bandwidth allocation tothe fabric.

Packet Transmit Queues 621.1.P, as shown, includes the four transmitqueues (Packet Transmit Queue #1 607.1.1 . . . Packet Transmit Queue #4607.1.4) of VNIC #1 600.1. Message Transmit Queues 621.1.M, as shown,includes two message transmit queues (Message Transmit Queue #5621.1.M.5 and Message Transmit Queue #6 621.1.M.6) of VNIC #1 600.1.(The above and subsequent uses of “ . . . ” can be read as “through.”)These correspond to the two message transmit queues identified by anactive message identified by each of Message Lists 615.1 (Message List#1 615.1.1 and Message List #2 615.1.2), as shown by dashed-ellipse614.1 (of FIG. 6A). The other 15 VNICs are organized identically.

Several levels of prioritization are performed to determine the nexttransmit descriptor to read (if not previously prefetched) and processwhen a new transmit descriptor is needed. Generally, the transmitdescriptors are prefetched in advance of their need. A firstprioritization level selects (identifies), for each VNIC, one packettransmit queue and one message transmit queue. The first level includesPacket Transmit Queue Prioritization 622.1.P, selecting one of PacketTransmit Queues 621.1.P according to either a straight or weightedround-robin priority scheme. The first level also includes MessageTransmit Queue Prioritization 622.1.M, selecting one of Message TransmitQueues 621.1.M according to either a straight or weighted round-robinpriority scheme. Identical prioritization processing is performed foreach of the 16 VNICs, selecting one potential packet queue and onepotential message queue for each VNIC. The resultant 32 candidate queuesare then evaluated in a second prioritization level.

The second prioritization level selects, for each VNIC, between thepacket queue or the message queue as selected by the firstprioritization level. The second level includes Packet vs. MessageTransmit Prioritization 623.1, selecting a packet queue or a messagequeue according to a weighted round-robin priority scheme. Identicalprioritization processing is performed for each of the 16 VNICs,selecting one candidate queue for each VNIC. These 16 queues are thenevaluated in a third prioritization level.

The third prioritization level selects, across the 16 VNICs, a singletransmit queue for subsequent evaluation. The third level includes VNICBandwidth Management 624, selecting one of the 16 queues provided by thesecond level according to a bandwidth allocation priority scheme.Bandwidth schemes include enforcing a maximum bandwidth per VNIC, aminimum bandwidth per VNIC, and arbitrary combinations of maximum andminimum bandwidths (individually selectable) per VNIC. A singleresultant transmit queue is selected for processing as indicated bydashed-arrow 639. The processing includes accessing a transmitdescriptor identified by the selected transmit queue, reading data fortransmission according to the accessed descriptor, and then readying thedata for transmission over the fabric in accordance to the VOQscheduling policy discussed in conjunction with FIG. 6C below.

The selection of straight or round-robin prioritization (Packet TransmitQueue Prioritization 622.1.P and Message Transmit Queue Prioritization622.1.M, for example) is individually programmable for each VNIC and maybe distinct for packet and message prioritization, in variousembodiments. Weights for each of the weighted round-robinprioritizations (Packet Transmit Queue Prioritization 622.1.P, MessageTransmit Queue Prioritization 622.1.M, and Packet vs. Message TransmitPrioritization 623.1, for example), are individually programmable, invarious embodiments. The maximum and minimum bandwidths per VNIC (VNICBandwidth Management 624) are also programmable in typical embodiments.

Once a transmit descriptor becomes scheduled in accordance with thetransmit-descriptor-fetch scheduling policy, the descriptor is fetchedand the first transfer is made (corresponding to a fabric-cell-worth ofdata) from the first packet in the transmit memory buffer pointed to bythe descriptor to a packet buffer in shared memory associated with thetransmit queue. This first read and the subsequent reads are performedby one or more transmit DMA engines, which operate in accordance withthe transmit-descriptor-fetch scheduling policy and thesubsequent-transmit-data-read scheduling policy, discussed below. Asdescribed elsewhere herein, a lookup is generally performed on the MACDAcontained in the first read, the nature of the destination becomes knownas a result of the lookup, and the data can subsequently beappropriately directed to either a multicast VOQ or afabric-port-specific unicast VOQ. Operation of the VOQs is discussed inmore detail below, in conjunction with FIG. 6C.

On a cell-by-cell basis as space becomes available in the appropriateVOQ, the data from the transmit queue packet buffer (in shared memory)is read, additional information is added (such as priority and thedestination fabric address and fabric sub-address), and the data istransferred to the appropriate VOQ as cells. As a matter of policy,cells from different packets are not co-mingled in the VOQs. The VOQsact as variable depth FIFOs, wherein the order in which cells enter aVOQ determines the order in which the cells leave the VOQ. As previouslyindicated, cells are released by the VOQs and transmitted to the fabricin accordance with the VOQ scheduling policy.

As data is transferred from the transmit queue packet buffers to theVOQs, the packet buffers are depleted. Responsive to the depletion, thesubsequent-transmit-data-read scheduling policy generally attempts tokeep the transmit queue packet buffers full of pre-fetched transmit readdata up to the allocated pre-fetch depth, which is 16 cache-lines in oneembodiment. In doing so, it gives higher priority to those transmitqueue packet buffers that are supplying cells for a packet that is atthe head of a VOQ (a packet being actively transferred as cells over thefabric). It gives lower priority to those transmit queue packet buffersthat are not yet supplying cells to a VOQ.

FIG. 6C illustrates selected aspects of a logical view of an embodimentof a VOQ scheduling policy to provide efficient access to the fabric.The figure represents processing to select the VOQ to send the next dataunit (cells in one embodiment) to the fabric. The VOQs send informationto the fabric interface as cells. Accordingly, at least logically theVOQ receives information as cells. Physically, the VOQ could receivecells as constituent components (data, priority, fabric address, etc.)and assemble the cells just prior to sending the cells to the fabricinterface. Furthermore, the VOQs may be implemented within the egressshared memory. Thus a number of levels of virtualization and indirectionare possible. In one embodiment, the VOQs are implemented within theegress shared memory and they hold cells that have been pre-assembledand are ready for immediate transfer via the fabric interface to theswitch fabric. The pre-assembly is performed at least in part bytransfers to each VOQ from an appropriately dynamically associatedtransmit queue packet buffer (also in the egress shared memory).

As indicated previously, transmit logic included in the VNICimplementation (such as in the egress logic of a VIOC as illustrated inFIG. 7A and as discussed below), assembles cells in preparation forproviding them to the VOQs as represented abstractly by dashed-arrow640. Included within each cell is a corresponding priority indication(one of four levels: P0, P1, P2, and P3, in selected embodiments) and acorresponding fabric destination address. The destination address may bea unicast address (one of up to 11 destinations, in some embodiments),or a multicast address. Multicast cells are enqueued into one ofMulticast Output Queues 641.M (also known as Multicast VOQs) accordingto priority, as abstractly represented by dashed-arrow 640.M,illustrating insertion into the P0 priority multicast VOQ.

Unicast cells are enqueued into one of 11 unicast VOQ groups (UnicastVOQ Group #1 641.1 . . . Unicast VOQ Group #11 641.11) according to thefabric destination address (VOQ Group #1 . . . VOQ Group #11) andfurther according to priority (P0 . . . P3) within each VOQ group. Sincethere are 11 destinations, each having four priorities, there are atotal of 44 unicast VOQs. The unicast enqueue operation is illustratedby dashed-arrows 640.1, and 640.11. Arrow 640.1 abstractly represents aunicast transmit cell addressed to the first fabric destination beingenqueued into the P1 priority VOQ of Unicast VOQ Group #1 641.1. Arrow640.11 abstractly represents a unicast transmit cell addressed to fabricdestination #11 being enqueued into the P2 priority VOQ of Unicast VOQGroup #11 641.11. For clarity, only two of the 11 Unicast VOQ groups ofidentical operation are shown in the figure.

Several levels of prioritization are performed to select the VOQ thatwill be permitted to send the next transmit cell to the fabric. A firstprioritization level selects a candidate VOQ from within the MulticastVOQs (Multicast Output Queues 641.M) and each of the Unicast VOQ groups(Unicast VOQ Group #1 641.1 . . . Unicast VOQ Group #11 641.11). Thefirst level includes Multicast Output Queue Prioritization 642.M,selecting a single multicast VOQ from Multicast Output Queues 641.Maccording to either a straight or weighted round-robin priority scheme.The first level also includes Unicast Output Queue Prioritization 642.1,selecting one of Unicast VOQ Group #1 641.1 according to either astraight or weighted round-robin priority scheme. Identicalprioritization processing is performed for each of the 11 Unicast VOQgroups, selecting one potential VOQ for each Unicast VOQ group. Theresultant 11 unicast VOQ candidates are then evaluated in a secondprioritization level, and the resultant single multicast VOQ candidateis then evaluated in a third prioritization level.

The second prioritization level selects, on a per VOQ group basis, oneof the 11 unicast VOQ group VOQ candidates as selected by the firstlevel. The second level includes Destination Prioritization 643,selecting a VOQ according to a round-robin priority scheme. Since theVOQ groups are organized by fabric destination, the second level is afabric-destination-based prioritization. The single result unicast VOQcandidate is then evaluated in the third prioritization level.

The third and final prioritization level selects between the multicastand unicast VOQ candidates as provided by the first and second levelsrespectively. The third level includes Multicast vs. Unicast OutputPrioritization 644, selecting the final multicast or the unicast VOQcandidate according to a weighted round-robin priority scheme. The finalselected VOQ is then permitted to provide one cell to the fabric, asabstractly represented by dashed-arrow 659.

The selection of straight or round-robin prioritization is individuallyprogrammable for Multicast Output Queue Prioritization 642.M and each ofUnicast Output Queue Prioritization 642.1 . . . 642.11. Weights for eachof the weighted round-robin prioritizations (Multicast Output QueuePrioritization 642.M, Unicast Output Queue Prioritization 642.1 . . .Unicast Output Queue Prioritization 642.11, and Multicast vs. UnicastOutput Prioritization 644, for example) are individually programmable,in various embodiments.

In some embodiments, the number of VOQ groups is equal to the number offabric destinations in the ES system (such as 11 VOQ groups and 11fabric destinations). In some embodiments, the number of VOQ groups isgreater than the number of fabric destinations (such as 16 VOQ groupsand 11 fabric destinations). In some embodiments, more than one prioritymay share a VOQ, instead of each priority having a separate VOQ. Forexample, P0 and P1 priorities may share a first VOQ within a VOQ groupand P2 and P3 priorities may share a second VOQ within the VOQ group.These and all similar variations are contemplated within the contexts ofvarious embodiments.

Ingress Path VNIC/Queue Operation

Shared receive resources include enqueuing bandwidth for cells receivedfrom the fabric. The bandwidth is shared based on a priority included inthe received data units (see the following FIG. 6D discussion). Afterenqueuing, the data units are classified according to destination VNICand associated queue, including processing according to multicast andunicast destinations. Then the data units are dequeued for storage intoLocal Processor Memory according to priorities associated with the VNICsand the queues of the VNICs. The shared receive resources furtherinclude the dequeuing bandwidth (see the following FIG. 6E discussion).

FIG. 6D illustrates selected aspects of a logical view of an embodimentto schedule the start of receive processing for incoming cells. Receivedcells are pushed into the VIOC from the fabric, typically via one ormore First-In-First-Out (FIFO) or similar buffering mechanisms externalto the VIOC, as suggested by dashed-arrow 660. As they enter, the cellsare classified according to multicast or unicast (dashed arrows 660.Mand 660.U, respectively), and inserted into Multicast Input Queues 661.Mor Unicast Input Queues 661.0 accordingly. In the illustratedembodiment, queue insertion is without regard to priority, as allpriorities (P0, . . . P3) share the same queue for a given traffic type.

As illustrated, a single level of prioritization is performed by thereceive logic to select an input queue from a candidate pool thatincludes Multicast Input Queues 661.M and Unicast Input Queues 661.U.The single level selects between the multicast and the unicast queuesaccording to Multicast vs. Unicast Input Prioritization 663, a weightedround-robin priority scheme. As abstractly represented by dashed-arrow679, the receive logic then pulls one cell from the queue selected forstorage into receive logic memory (such as ISMem 738) and subsequentprocessing. Weights for Multicast vs. Unicast Input Prioritization 663are individually programmable, according to various embodiments.

In a variation of FIG. 6D, some embodiments select the next cell to pullfrom the input queues at least in part according to prioritiesassociated with the received cells. For example, the multicast andunicast input queues may be managed with priority information eitherincluded in the received data unit or determined as a function of thefabric transport priority associated with the received cell, accordingto embodiment. Multicast and unicast input queue insertion is thenpartially determined by the priority associated with the received cell,in addition to multicast versus unicast categorization. Multicast InputQueues 661.M and Unicast Input Queues 661.0 are thus each modified to beorganized with respect to data unit priority.

In some embodiments, there are four defined priority levels (P0, P1, P2,and P3), and each queue includes data associated with a single priority(i.e. there is a queue per categorization and priority pair). In someembodiments, each queue may include cells from a pair of priorities (P0and P1 in a first queue, and P2 and P3 in a second queue, for example).In other embodiments, queue insertion is further determined according toinformation provided in response to a lookup operation based oninformation included in the received cell (see the TCAM/SRAM lookupstate section, elsewhere herein).

In embodiments of FIG. 6D modified to have queues partially managed bypriority, a first prioritization level selects, on a per queue prioritybasis, one candidate multicast input queue and one candidate unicastinput queue from the multicast and unicast input queue groupsrespectively. The first prioritization may be straight priority,straight round-robin, or weighted round-robin, according to embodiment.The resultant two input queue candidates are then evaluated in a secondprioritization level. The second prioritization level selects betweenthe multicast and unicast input queue candidates according to a straightpriority, straight round-robin, or weighted round-robin, according toembodiment.

In some embodiments that include priority-managed receive path inputqueues, at least some of the queues may be implemented with queue depthssubstantially larger than queue depths implemented for embodimentslacking priority-managed queues. In some of these embodiments havingpriority-managed queues, the receive path input queue depths aresubstantially larger than the effective queue depth of the fabricproviding the receive data units.

In some embodiments, selected received cells are ignored (or dropped)according to programmable receive (or ingress) bandwidth limitations orpolicies, to prevent overuse of subsequent VIOC receive resources orassociated Local Processor resources. In various embodiments, theingress bandwidth limitation policies operate in parallel with theprioritization illustrated in FIG. 6D, and in various other embodimentsthe ingress policies operate either “before” or “after” the operationsdepicted in the figure. Some embodiments implement dropping policiesaccording to a single cell, while other embodiments drop all subsequentcells of a packet or a message after dropping a first cell in responseto a dropping policy operation.

Incoming unicast cells have a fabric sub-address that identifies theVNIC and receive queue to which the cell is associated. As each unicastcell is pulled from the unicast queue, the receive queue is ascertainedand the data payload of the cell is placed into a corresponding receivequeue packet buffer. The data carried by multicast cells is replicatedin accordance with the multicast group ID and appropriately placed intomultiple receive queue packet buffers. The data held within the receivequeue packet buffers accumulates until written to Local Processor Memoryin accordance with a receive-data-write scheduling policy, asillustrated in FIG. 6E.

The receive-data-write scheduling policy of FIG. 6E selects the nextreceive queue to be serviced. The queue selection determines the nextreceive data to write through the following indirection. Each receivequeue points to a currently active receive descriptor, which describes areceive buffer in the Local Processor Memory that is ready to receiveone or more packets. Each receive queue also has a corresponding receivequeue packet buffer in the ingress shared memory. The receive data to benext written is the data unit (generally a cache-line in memory)identified by the next data unit write pointer of the receive queuepacket buffer corresponding to the receive queue selected by thereceive-data-write scheduling policy from the candidate pool of all VNICreceive queues. The selection is based in part on a prioritization amongthe VNIC receive queues, in a manner that is configurable in part. Eachdata unit written is scheduled independently (generally on a cache-lineby cache-line basis) by the receive-data-write scheduling policy. Thewrites associated with each receive descriptor carry out the reassemblyof corresponding data link layer frames (typically Ethernet frames).

For clarity, only two of the 16 VNICs (VNIC #1 600.1 and VNIC #16600.16) are illustrated in FIG. 6E. Packet Receive Queues 684.1.P, asshown, includes four packet receive queues such as Packet Receive Queue#1 684.1.P.1 and Packet Receive Queue #4 684.1.P.4 of VNIC #1 600.1.These correspond to the four packet receive queues identified by each ofPacket Receive Queue Pointer #1 608.1.1 . . . Packet Receive QueuePointer #4 608.1.4 respectively (of FIG. 6A). Message Receive Queues684.1.M, as shown, includes two message receive queues (Message ReceiveQueue #5 684.1.M.5 and Message Receive Queue #6 684.1.M.6) of VNIC #1600.1. These correspond to the two message receive queues identified byan active message identified by each of Message Lists 615.1 (MessageList #1 615.1.1 and Message List #2 615.1.2), as shown by dashed-ellipse614.1 (of FIG. 6A). The other 15 VNICs are organized identically.

Several levels of prioritization are performed to select the nextreceive queue. A first prioritization level selects, for each VNIC, onecandidate packet receive queue and one candidate message receive queue.The first level includes Packet Receive Queue Prioritization 682.1.P,selecting one of Packet Receive Queues 684.1.P according to a straightround-robin priority scheme. The first level also includes MessageReceive Queue Prioritization 682.1.M, selecting one of Message ReceiveQueues 684.1.M according to a straight round-robin prioritizationscheme. Identical processing is performed for each of the 16 VNICs,selecting one potential receive packet queue and one potential receivemessage queue for reach VNIC. The resultant 32 candidate queues are thenevaluated in a second prioritization level.

The second processing level selects, for each VNIC, between the packetor the message receive queue as selected by the first prioritizationlevel. The second level includes Packet vs. Message ReceivePrioritization 681.1, selecting a packet or a message receive queueaccording to a straight round-robin priority scheme. Identicalprioritization processing is performed for each of the 16 VNICs,selecting one candidate receive queue for each VNIC. These 16 candidatedata units are then evaluated in a third prioritization level.

The third and final prioritization level selects, across the 16 VNICs, asingle receive queue. The third level includes VNIC Prioritization 680,selecting one of the 16 receive queues provided by the second levelaccording to a straight round-robin priority scheme. A final singleresultant receive queue is selected and, through the indirection processdescribed previously, a single data unit (generally a cache-line) iswritten via the HT interface into Local Processor Memory as abstractlyrepresented by dashed-arrow 699.

In some embodiments, weighted round-robin prioritization may beperformed for any combination of the first, second, and thirdprioritization levels, and the associated weights may be fixed orindividually programmable, according to embodiment. Various embodimentsmay also provide individual programmable selection between straight andweighted round-robin for each of the first, second, and thirdprioritization levels.

Queue Priorities

Transmit and receive priority algorithms may vary according toembodiments. For example, in some embodiments, straight priority mayimplement a static priority having queue #1 as the highest, queue #2 asthe next highest, and so forth with queue #4 as the lowest priority. Inother embodiments, the priority order may be reversed (i.e. #4 is thehighest and #1 is the lowest). In some embodiments, instead of weightedround-robin, straight, or simple (i.e. un-weighted round-robin) may beimplemented. Round-robin weighting may be based on data units (cells,for example) or bytes, according to various embodiments. Weighted fairqueuing may also be provided by some embodiments in place of or inaddition to weighted round-robin, and the weighted fair queuing may bebased on data units or bytes, according to various embodiments.Round-robin processing may be based on previously processed informationor on queue depth, also according to embodiment.

VLAN Overview

In some embodiments, each VNIC is a member of one VLAN, which is aport-based VLAN (i.e., a virtual LAN defined by logical connection to adesignated subset of available logical L2 switch ports). In otherembodiments, each VNIC may be a member of a plurality of VLANs,including at least one port-based VLAN. In various embodiments, theVLANs may be port-based, MAC address-based, IP address-based, and L3type VLANs. VLANs may be provisioned and managed by programming VNICaddress information accordingly (such as VLAN Identifier 617.1, forexample) and by writing corresponding lookup state (such as thatretained in TCAM/SRAMs). VLAN management operations may be relativelystatic, as related to endpoints included within a server, or relativelydynamic, as related to endpoints external to the server. Internalendpoint VLAN operations include server and cluster provisioning andre-provisioning, VLAN specific provisioning, pluggable module insertionand removal, and failover responses, for example. VLAN operations may besupervised by controlplane processes executing on a SCM (such as PrimarySCM 140A), Driver processes executing on Local Processors, orcombinations of the two, according to embodiment.

In some embodiments, VLAN related processing for egress data to thefabric includes determining a VLAN identifier. If the VLAN identifierdoes not match the source VLAN identifier, then the egress data mayoptionally be dropped, according to embodiment. The source VLANidentifier may be provided directly from VLAN Identifier 617.1 orderived from it, according to embodiment. If the destination MAC is notidentifiable, then the egress data may be flooded to all destinationsallowed by the source VLAN configuration, according to embodiment.

In some embodiments, VLAN related processing for ingress data from thefabric includes determining which VNICs, if any, are members of the VLANidentified by the received data, and providing the data to the memberVNICs appropriately. If no VNICs are members of the destination VLAN,then the ingress data may be optionally dropped, according toembodiment. In some embodiments, VLAN related broadcasts to VNICs may bewholly or partially implemented using multicast group processing. VLANingress processing may optionally include determining the VLANidentifier associated with learning a MAC Source Address (MACSA)associated with the ingress data. Optionally processing may furtherinclude dropping the ingress data if the learning VLAN (i.e. the VLANfrom which the MACSA was learned from) is different from the destinationVLAN.

In some embodiments, VLAN broadcasts are implemented by assigning aMulticast Group IDentifier (MGID) to each of the VLAN broadcast groups.In one embodiment there are 32K available MGIDs sharable between VLANand IP broadcast groups.

Some embodiments implement Independent VLAN Learning (IVL), otherembodiments implement Shared VLAN Learning (SVL), and still otherembodiments implement IVL and SVL modes and configurable selectionbetween them. IVL and SVL both enforce inter-VLAN isolation (within thesame abstraction layer) through confirmation of VLAN membership based onMAC address. In IVL, forwarding entries (i.e., entries of the FIBs) areshared throughout the VLAN on which they are learned, but are not sharedwith other VLANs. In SVL, forwarding entries learned on a first VLAN are“shared” with other VLANs. Under SVL, a forwarding entry learned for aMAC address on a first VLAN (and therefore unreachable at the sameabstraction layer by other VLANs) is used by the other VLANs for thelimited purpose of dropping frames addressed to the MAC address on thefirst VLAN. The MAC address is known by the other VLANs to beunreachable only because of the SVL sharing. In this way, SVL preventsunnecessary flooding within any of the other VLANs, which under IVLwould have occurred in a futile effort to reach the MAC address on thefirst VLAN (which under IVL, is guaranteed to be unknown to the otherVLANs). Further details of IVL and SVL, particularly with respect toTCAM/SRAM configuration and use, is provided in conjunction with thediscussion of FIGS. 8A and 8B.

Static VLAN management operations typically include distribution of VLANmembership information, removing the need for learning VLAN membershipchanges relating to provisioning, module insertion and removal, andfailover responses. Typically VLAN learning operations are performedunder the supervision of SCM-based management processes.

VIOC Internals

As previously described, at least one VIOC is included in each of PMM150A, OLB 160A, FCM 120A, and each of the SCMs 140 (including PrimarySCM 140A). Each VIOC typically implements functionality for a pluralityof VNICs. The VIOC is illustrated in these various operating contexts inFIGS. 3A, 4A, 4B, 4D, and 4E. VIOC operation was summarized in thepluggable modules section above, in conjunction with an examination ofVIOC 301.4 of FIG. 4A. As shown in FIG. 3A, the VIOC 301.5 is coupledand adapted to directly communicate packets 351 between RAM elements 350and the Primary Switch Fabric Module 180A. The RAM elements are alsoaccessible by one or more CPUs, enabling processes executing on the CPUsto directly exchange data via the fabric. With reference particularly toFIG. 4A and 4B, CPUs coupled to RAMs accessible by VIOCs in this mannerare examples of Local Processors, and the coupled RAMs are examples ofLocal Processor Memory. RAM elements 411.4L and 411.4R are accessiblevia an HT Channel 460.4R, and the fabric is accessible via a CommonSwitch Interface consortium (CSIX) channel 149A.

The transmission and reception of packet (and message) data directlybetween Local Processor Memory and the fabric corresponds to dataplanefunctionality. Control of dataplane functionality corresponds tocontrolplane functionality and conceptually includes forwarding tablesand related state information included in part in the TCAM/SRAM. Controlpackets (also known as VIOC-CP packets) generated by the SCM arereceived via the fabric and processed by the VIOCs, resulting inselective accesses to configuration registers and the TCAM/SRAM coupledto each VIOC. The forwarding and state information of the TCAMs/SRAMs istypically initialized and maintained in this way. In variousembodiments, the control packets are provided by management andcontrolplane processes executing on any combination of the SCMs, PMMs,and OLBs. Configuration information of a more general nature istypically provided in part by a BMC.

The VIOC and processes executing on the Local Processors communicate inpart by sharing portions of the Local Processor Memory space. Includedin these shared portions are the packet and message queues as describedin the VNIC overview and queuing operation section. In addition, theVIOC itself appears as an intelligent memory-mapped I/O device residingin a portion of the Local Processor Memory space. In this way, the VIOCprovides access to configuration registers and certain state relating topacket (and message) transmission and reception.

The packet transmit and receive descriptors associated with the VNICsdescribe raw data buffers in the Local Processor Memory where packetdata is respectively read and written by the VIOC, via DMA operations,in order to implement VNIC functions. In some embodiments, at least someof the packet transmit and receive descriptors are prefetched intobuffers onto the VIOC to improve performance In certain embodiments, allof the packet receive descriptors corresponding to the VIOC's VNICs arebuffered. When reference is made herein to one or more descriptorswithin or on the VIOC, those skilled in the art will understand thatsuch descriptors are the buffered copies of the same descriptors withinthe Local Processor Memory. The VIOC operates on the completion queuesdirectly in the Local Processor Memory.

In certain embodiments, the packet CSB's are held within the VIOC toimprove performance The message context state is kept in either theLocal Processor Memory, or in memory private to the VIOC (such as theTCAM/SRAM or the DDR DRAM discussed herein below). Since in certainembodiments the packet CSBs that represent the packet queues are heldon-chip, and since some descriptors are buffered on-chip, for someconceptual purposes the queues may be thought of as residing within theVIOC. Those skilled in the art will understand that this is an informalabstraction, as the queues actually reside in Local Processor Memory.

Packet and message transmission corresponds to data flowing out from theVIOC to the fabric, also known as VIOC egress, or simply as egress whendiscussing the VIOC operation. Conversely, packet and message receptioncorresponds to VIOC ingress, or simply ingress.

FIG. 7A illustrates selected aspects of one VIOC embodiment as VIOCblock diagram 700A. Included in VIOC 301 are several interfaces,including a unit for coupling to Double Data Rate (DDR) DRAM memories(DDR Interface 701) via coupling 721, a unit for coupling to an HTchannel (HT Interface 702) via coupling 722, and a block for coupling toa BMC (BMC Interface 718 included in VIOC Control 704) via coupling 733.

Further included in VIOC 301 are FICTX 714 (an instance of a VIOC fabricinterface communication transmit unit) and FICRX 715 (an instance of aVIOC fabric interface communication receive unit). FICTX 714 includesegress path elements Vioc EGRess interface (VEGR) 708, and CSix Transmitunit (CSTX) 710. VEGR 708 includes DMATX 716, an instance of a transmitDMA unit; ECSM 735, an instance of Egress Control State Machines; andESMem 736, an instance of an Egress Shared Memory. FICRX 715 includesingress path elements Vioc INGress interface (VING) 709, and CSixReceive unit (CSRX) 711. VING 709 includes DMARX 717, an instance of areceive DMA unit; ICSM 737, an instance of an Ingress Control StateMachines; and ISMem 738, an instance of an Ingress Shared Memory that insome embodiments is an implementation of the receive logic memory.

Flow control blocks Csix Flow Control Unit Transmit side (CFCUTX) 712and Csix Flow Control Unit Receive side (CFCURX) 713, included in VIOC301, are coupled from the receive path to the transmit path. Asdescribed in more detail elsewhere herein, CFCUTX 712 is used totemporarily suspend sending by CSTX 710 upon receiving an indication offabric congestion and CFCURX 713 is used to indicate VIOC congestion toother modules. Other VIOC elements include RXDmgr 766, and shared egressand ingress elements Lookup Engine (LE) 703 and Message State Machine707. VIOC 301 control elements include VIOC Control 704, in turnincluding SIM Interface 705, VIOC Configuration block 706, and BMCInterface 718.

For clarity and emphasis, only selected egress and ingress data flowsare indicated explicitly in the figure. Generally, egress data entersVIOC 301 via HT Channel coupling 722, and flows from HT Interface 702 toVEGR 708 via coupling 750, under control of DMA read protocolsimplemented by DMATX 716. The egress data continues to CSTX 710 viacoupling 751, exiting CSTX 710 via coupling 753, and exits VIOC 301 viaFabric Coupling 732. Similarly, ingress data flows in a symmetricreverse path, entering via Fabric Coupling 732 and continuing to CSRX711 via coupling 763 and then to VING 709 via coupling 761. The ingressdata proceeds to HT Interface 702 via coupling 760 under control of DMAwrite protocols implemented by DMARX 717 to exit VIOC 301 via HT Channelcoupling 722.

Information related to egress flow control is provided from CSRX 711 toCFCUTX 712 via coupling 752 r. Egress flow control commands are providedfrom CFCUTX 712 to CSTX 710 via coupling 752 t. Information related toingress flow control is provided from CSRX 711 to CFCURX 713 viacoupling 762 r. Ingress flow control commands are provided from CFCURX713 to CSTX 710 via coupling 762 t. Control packet handshaking isprovided from FICRX 715 to FICTX 714 as shown by ingress-egress coupling772.

Although couplings 750, 751, 753, 760, 761, 763, and 772 are illustratedas unidirectional, this is only to highlight the primary flow of data,as control and status information, for example, flows along similarpathways in a bidirectional manner Internal egress path related coupling770 and ingress path related coupling 771 illustrate LE 703 request andreturning status and result communication with VEGR 708 and CSRX 711,respectively.

VIOC Configuration block 706 includes configuration and mode informationrelating to operation of VIOC 301, generally organized into registers,including system configuration registers and local configurationregisters. The system and local configuration registers are typicallyaccessed by management processes executing on Primary SCM 140A, bycontrol packets sent to Fabric Coupling 732, and then processed by CSRX711 and SIM Interface 705. The system registers are typicallyinaccessible to processes executing on Local Processors, and include aplurality of scratchpad registers typically used for communication withthe management processes. However, the local registers are typicallyaccessible via the HT channel by Hypervisor, OS, and Driver processesexecuting on Local Processors. Hypervisor and OS processes typicallyconfigure environments for Application processes so that the localconfiguration registers are inaccessible to the Application processes.

The system registers include VNIC related registers, such as AddressBlock 601.1 (of FIG. 6A) for each of 16 VNICs. Also included is a bit(or mask) per VNIC to enable and disable the corresponding VNIC. Thelocal registers include pointers and state information associated withI/O Block 605.1 (of FIG. 6A) of each of the 16 VNICs.

During initialization and debug, Local Processor access to the systemregisters may be provided by manipulation of a field in the systemconfiguration registers. In addition, the system and local configurationregisters are accessible via BMC command and data information receivedfrom BMC Interface 718.

In one embodiment, VIOCs included on controlplane modules (such as SCMsincluded in SIMs) are initialized by BMC commands to enable selectedprivileged operations, including transmission via the fabric of controlpackets without lookup processing (these packets are also referred to as‘No Touch’ packets). No Touch packets may be used for control packets(to initialize or modify forwarding information included in TCAM/SRAMs)and to forward an exception packet from an SCM to the properdestination. VIOCs included on other modules (such as PMMs, OLBs, andFCMs) are initialized to disable No Touch packet transmission, i.e.packets (and messages) are always processed with an egress lookup.

SIM Interface 705 is coupled to receive control packets from CSRX 711 astypically provided by controlplane processes executing on an SCMincluded in a SIM. The control packets are parsed to determine theincluded command and any associated parameters, such as address anddata. SIM Interface 705 then passes the command and parameters to theproper element of VIOC 301 for execution. Return handshake status istypically provided in the form of a packet addressed to the sending SCMfrom FICRX 715 to FICTX 714 via ingress-egress coupling 772, and FICTX714 provides the packet to the fabric.

BMC Interface 718 includes logic for interfacing to a BMC, includingreceiving, processing, and responding to BMC commands received viacoupling 733. The interface parses the command, provides the command andany associated parameters to the proper unit of VIOC 301, and returnsresponse information as appropriate.

HT Interface 702 includes an HT Channel compatible external interfaceproviding read and write style accesses to resources available viacoupling 722. Read response information (typically associated withegress processing) is provided to VEGR 708 via coupling 750. Writeinformation (typically associated with ingress processing) is providedfrom VING 709 via coupling 760. In a typical usage scenario, the readand write accesses target memory locations in RAMs coupled to CPUscoupled in turn to HT Channel coupling 722 (i.e. Local ProcessorMemory). HT Channel coupling 722 is an illustrative instance of HTcouplings including 460.4R, 460.5R, 460.5R′, 460.6R (of FIGS. 4A, 4B,4B, and 4E, respectively).

DDR Interface 701 includes logic for coupling to DDR DRAMs via coupling721. DDR Interface 701 communicates with Message State Machine 707 viacoupling 767, as shown. DDR Interface 701 also communicates with otherelements of VIOC 301 via implicit communication paths that allow accessto the DRAMs via control packets (SIM Interface 705), BMC commands (BMCInterface 718), and processes executing on Local Processors (HT Channelcoupling 722), in addition to VIOC internal requests (Message StateMachine 707, VIOC Control 704, FICTX 714, and FICRX 715). The topologyof these paths will be understood by those of ordinary skill in the art.In various embodiments, DDR SDRAM typically includes data structuresrelated to context and message related processing (such as CSBs), aswell as virtual to physical address translation for transmit and receivebuffer addresses in Local Processor Memory.

Message State Machine 707 manages message state (including connecting,established, closing, and closed) for a plurality of message contexts,such as those associated with the 16 VNICs, according to aconnection-oriented reliable protocol. According to embodiment, messagestate is stored in part in DDR coupled via coupling 721 to DDR Interface701, and coupling 767 communicates requests for DDR reads and writes, aswell as resultant read data between the state machine and the DDRinterface. The state machine also provides for message handshaking andre-delivery attempts by appropriate processing and communication withFICTX 714 and FICRX 715, via implicit couplings that will be understoodto those of ordinary skill in the art. For example, message relatedinspection and processing of incoming information may be performed inCSRX 711 under the direction of Message State Machine 707. Similarly,message related processing and information insertion may be performed inCSTX 710 also under the control of the state machine. Further includedin Message State Machine 707 are logic units for performing RDMA.

RXDmgr 766 includes logic for fetching and prefetching receivedescriptors to support ingress operation. Receive descriptorrequirements and results are communicated with FICRX 715 via coupling764. Requests to read descriptors from Local Processor Memory areprovided to HT Interface 702 via coupling 765, and returning data isreturned via coupling 765.

FICTX 714 includes logic (VEGR 708) implementing egress path processing,including accessing packet data for transmission and cellification usingDMA protocols, according to configured priorities and bandwidthallocations, and including one lookup (LE 703 via coupling 770). Thelookup typically provides a fabric egress port based in part on thepacket destination address (typically a MAC address) and relevant VLANrelated information. The included logic also implements packet datacellification and CSIX cell-level processing (CSTX 710). An overview ofselected aspects of packet access and cellification is provided withrespect to FIG. 3A. In some embodiments, FICTX 714 processes selectedmulticast packets (and hence cells) using cell-level multicastcapability provided by the fabric.

VEGR 708 includes logic blocks performing packet egress processingfunctions including transmit queue management and scheduling (see FIG.6B and the related discussion), transmit packet scheduling, packetsegmentation into cells (including a packet address processing lookupvia LE 703), various control state machines within ECSM 735, and anegress shared memory ESMem 736. DMATX 716, included in VEGR 708, isconfigured to transfer packet image data from Local Processor Memory tothe egress shared memory, and further configured to transfer data fromthe egress shared memory to CSTX 710. In an illustrative embodiment, theVOQs are implemented as pointer managed buffers that reside within theegress shared memory. The DMA transfers are managed by the control statemachines in VEGR 708 according to bandwidth and priority schedulingalgorithms.

CSTX 710 includes logic blocks performing cell egress processingfunctions. Logic units in CSTX 710 read cell data according to the VOQsas scheduled by a VOQ prioritizing algorithm (see FIG. 6C and therelated discussion), calculate horizontal parity, vertical parity, andCRC for each cell, and then send the results and the cell data to thefabric. Logic units in CSTX 710 include CSIX egress queue structures andassociated transmit data path (FIFO) buffers, CSIX compatible transmitflow control logic responsive to information received from CFCUTX 712,logic responsive to information received from CFCURX 713 (to applyfabric back-pressure using CSIX compatible receive flow controlinstructions), and a transmit-side CSIX compatible external interfacefor Fabric Coupling 732.

CFCUTX 712 (shown outside of FICTX 714 in the figure, but closelyassociated with egress processing) includes fabric congestion detectionlogic and VOQ feedback control logic to instruct CSTX 710 to stopsending cell traffic from a VOQ when fabric congestion is detected. Whenthe congestion is relieved, the logic instructs CSTX 710 to resume celltraffic from the stopped VOQ. Fabric congestion information is providedto CFCUTX 712 from CSRX 711 as it is received from the fabric.

The VOQ prioritizing algorithm implemented in CSTX 710, as illustratedin FIG. 6C, includes configurable weighted round-robin priority betweenunicast output queues and multicast output queues, round-robin priorityamong VOQ groups, and straight priority within VOQ groups. The algorithmalso guarantees that all cells associated with a given packet are sentin order, and further that cells from different packets from the sameVOQ are not intermingled. In other words, once a first cell for a packetfrom a selected one of the VOQs is sent, then the remainder of the cellsfor the packet are sent before any cells of any other packet from theselected VOQ are sent.

FICRX 715 includes logic implementing ingress path processing, includingCSIX cell-level processing (CSRX 711), and packet-level processing (VING709), including storing reassembled packets using DMA protocols. Anoptional lookup (LE 703) is performed under the control of CSRX 711 viacoupling 771. The lookup provides information related to processing thepacket, including mapping the packet to the proper receive queue.

CSRX 711 includes logic blocks performing cell ingress processingfunctions. Logic units in CSRX 711 receive, buffer, and parse cell datafrom the fabric. Logic units in CSRX 711 include a receive-side CSIXcompatible external interface for Fabric Coupling 732, CSIX ingressqueue structures and associated CSIX receive data path (FIFO) buffers, aCSIX cell parser unit, and transmit and receive flow control informationdetection logic.

CFCURX 713 (shown outside of FICRX 715 in the figure, but closelyassociated with ingress processing) includes VIOC congestion detectionlogic and fabric feedback control logic to instruct the fabric to stopsending cell traffic of a specific priority when VIOC congestion isdetected for that priority. When the congestion is relieved, the logicinstructs the fabric to resume cell transmission. Receive flow controlinstructions to the fabric are communicated via CSTX 710. This method ofcongestion relief is referred to elsewhere herein as applying fabricback-pressure.

Cell data is received from the fabric, including horizontal parity,vertical parity, and CRC. The parities and CRC are computed for thereceived data, checked, and errors logged. Cell and packet headers areparsed, and in some embodiments an optional lookup is performed (LE 703)for selected unicast packets to determine in part an appropriate receivequeue. In some embodiments, an optional lookup is performed formulticast packets, VLAN broadcast packets, or both, according toembodiment, to determine in part one or more appropriate receive queuesor multicast group identifiers, also according to embodiment. Unicastlookups (if performed) are typically based in part on a source fabricport address and a context key included in the packet header. Someembodiments omit unicast lookups entirely. Control packet data iswritten into a control packet portion of the CSRX's FIFOs, andsubsequently sent to SIM Interface 705 for further processing, whilenon-control packet data is written to a data portion of the CSRX'sFIFOs.

VING 709 includes logic blocks performing packet ingress processingfunctions including receive and completion queue management andscheduling, receive packet scheduling (see FIG. 6D and the relateddiscussion), cell reassembly into packets, various control statemachines, and an ingress shared memory. DMARX 717, included in VING 709,is configured to transfer cell data into Local Processor Memory from theIngress Shared Memory (ISMem 738). The DMA transfers are managed by theIngress Control State Machines (ICSM 737) in VING 709. A receive bufferis considered complete (or consumed) when either the last availablelocation in a buffer is written, or the last cell of a packet iswritten. Buffer completion is indicated by writing an entry to one ofthe completion queues, with data including packet receive status (Erroror OK), receive processing (or thread) number, and context key (if thedata includes the last cell of the packet). The completion queue writeinformation optionally includes results of packet-level CRC and 1'scomplement computations for use by Driver or other processes executingon the Local Processors.

VING 709 controls movement of cell data from the ingress shared memory(ISMem 738) to Local Processor Memory during packet reconstructionaccording to various receive scheduling algorithms (see FIG. 6E and therelated discussion), including determination of buffers in the LocalProcessor Memory, selection of cell data to transfer, and movement ofthe packet data to the Local Processor Memory. Buffers are determined byprocessing receive descriptors, and in some embodiments the receivedescriptors are fetched and processed according to a round-robinpriority between the groups of receive queues. Cell data is scheduledfor transfer to the Local Processor Memory according to a selectionbetween unicast and multicast queues for insertion into the receivequeues, as illustrated by FIG. 6D. This is followed by a weighted roundrobin-scheduling algorithm between the groups of receive queues, asillustrated by FIG. 6E, according to various embodiments. Packet datamovement into the Local Processor Memory is also directed in partaccording to flow control information from HT Interface 702 that VING709 responds to in order to prevent overrunning limited resources in theHT interface.

Fabric Coupling 732, in one embodiment, includes a Fabric Interface Chip(FIC) providing low-level functions relating to coupling to anembodiment of SFM 180 that includes Fabric Switch Chips (FSCs). FabricCoupling 732 is an illustrative instance of generic fabric couplings,which in the system as a whole further includes FCM-Fabric coupling129A, NM-Fabric coupling 139A, OLB-Fabric coupling 169A, PMM-Fabriccoupling 159A, and PMM-Fabric coupling 159A′, for example.

LE 703 includes TCAM and SRAM interfaces, and accepts egress lookuprequests from VEGR 708 and ingress lookup requests from CSRX 711. Lookuprequests include a key and a look up transaction identifier. The TCAM issearched for a first entry matching the key, and if a match is found, acorresponding entry from the SRAM is read. When processing is completeand lookup information available, the requestor is notified by ahandshake, and the transaction identifier, a match indication, andresult data (if a match) are returned to the requestor (one of VEGR 708and CSRX 711). Request processing is pipelined in LE 703, but if theLookup Engine is unable to accept a request, then an acceptance delayedindicator is provided to the requestor. In one embodiment the key andthe results are each 64 bits, both are multiplexed in two 32-bit chunks,and the transaction identifier is 4 bits.

In addition to lookup requests during egress and ingress processing, LE703 supports directly reading and writing the TCAM and SRAM to examineand modify lookup information, via requests from BMC Interface 718, SIMInterface 705, and HT Interface 702.

In operation, VIOC 301 and related components are initialized to setconfiguration, mode, initial state, and other related information. Forexample, selected management and configuration control informationmaintained in VIOC Configuration block 706 is written by an external BMCvia coupling 733 and BMC Interface 718. Additional information isoptionally written by an external agent via packets received from FabricCoupling 732, CSRX 711, and SIM Interface 705. Additional informationmay also be optionally written by an agent coupled to HT Channelcoupling 722 via HT Interface 702. Typically, the management andconfiguration control information is provided by management processesexecuting on Primary SCM 140A, as described elsewhere herein.

Initial (as well as subsequent) ingress and egress lookup information,including forwarding, VLAN, and multicast information, is typicallyprovided by controlplane and related processes executing on Primary SCM140A. The information is included in packets sent by the processes andreceived via Fabric Coupling 732, CSRX 711, and SIM Interface 705. Thelookup information is stored in TCAM/SRAM resources coupled to VIOC 301via TCAM/SRAM coupling 723 by LE 703. Portions of state stored in theTCAM/SRAM may also be optionally initialized by the agent coupled to HTChannel coupling 722 via HT Interface 702 and LE 703.

After initialization, VIOC 301 and related elements are available fordirectly communicating packets (and messages) between clients coupled tothe fabric, as described with respect to FIG. 3A and FIG. 4A. Thecommunication is bidirectional, including egress (from Local ProcessorMemory to fabric) and ingress (from fabric to Local Processor Memory),and is typically accessible to processes executing on Local Processorsvia a VNIC-style interface as illustrated by FIG. 6A.

Egress operation serves to directly transmit a buffer of packet data, asprovided by a Driver process in conjunction with an OS executing on aLocal Processor, to the fabric. The Driver (or optionally an Applicationprocess) forms a packet image within the buffer. A transmit descriptor,including the physical address of the buffer, the buffer size, a validindicator, and a done indicator, is fabricated by the Driver and placedon one of the transmit descriptors. The valid indicator is asserted bythe Driver to indicate the descriptor is ready for processing by VIOC301. The done indicator is initially deasserted by the Driver and laterasserted by VIOC 301 when the descriptor and the underlying buffer datahas been fully processed by the VIOC. Upon assertion of done the bufferis available for subsequent use by the Driver.

After forming the packet image and the transmit descriptor, in oneillustrative scenario, the Driver informs VIOC 301 that additionalpacket data is available for transmission by accessing a correspondingDoorbell, asynchronously interrupting VIOC 301. The Doorbell access issent via HT Channel coupling 722, received by HT Interface 702, andprocessed by VIOC Control 704. In another illustrative scenario, insteadof the Doorbell access, VIOC 301 polls transmit descriptors, examiningthe associated valid indicators, to determine that additional packetdata is available for transmission.

When additional packet data is available for transmission, VEGR 708accesses the transmit queue using DMA processing functions included inDMATX 716 according to the bandwidth and priority scheduling algorithmsof FIG. 6B. Algorithms implemented by the priority scheduling of thetransmit queue accesses include straight priority, round-robin, andweighted round-robin, and priority is determined between transmit packetqueues and transmit message queues. The information obtained from thequeue includes a descriptor including a pointer to the new packetimages. VEGR 708 analyzes the descriptor, providing the pointer to DMATX716 and requesting additional accesses to begin to read in the packetimage. The packet image begins with a packet header, including packetdestination and priority information. VEGR 708 formats information fromthe packet header, including the destination, along with VLAN processingrelated information, into a lookup request in a suitable format, andpasses the request to LE 703. LE 703, in turn, accepts the request whenroom for the request is available, and processes it by accessing thecoupled TCAM/SRAM. The lookup result, including a destination fabricport address, is used in forming appropriate cell headers, including afabric destination port address. Packet data is cellified and sent toCSTX 710 for further processing.

CSTX 710 receives the cellified packet data, including cell headerinformation, and processes the data according to the VOQ prioritizingalgorithms of FIG. 6C. Cell data is sent according to the configuredpriority algorithm, and CSTX 710 is further responsive to flow controlinstructions received from CFCUTX 712. Cell parities and CRC arecalculated and provided to Fabric Coupling 732 along with the cellheader and data information.

Ingress operation is conceptually the reverse of egress operation, andserves to directly receive packet data into a buffer in Local ProcessorMemory, the buffer being directly accessible by a Driver process (andoptionally an Application process) executing on a Local Processor. Areceive descriptor, including the physical address of the buffer, thebuffer size, and a valid indicator, is fabricated by the Driver andplaced on one of the receive descriptor queues. The valid indicator isasserted by the Driver to indicate the descriptor is ready for use byVIOC 301. Typically VIOC 301 prefetches (under the direction of RXDmgr766) and preprocesses one or more receive descriptors in preparation forreceiving cell data and storing it into a new receive buffer in LocalProcessor Memory. A completion queue entry is written by VIOC 301 whenthe buffer has been filled with packet image data.

CSRX 711 receives CSIX cells, checks parities and CRC for the receivedcells, parses cell headers, and for the first cells of packets, parses apacket header. Information related to flow control is provided to CFCURX713, and fabric back-pressure is applied (via CSTX 710) when VIOCcongestion is detected. A lookup is performed via LE 703 for the firstcells of multicast packets, to determine proper destinations andrequired replication of the packet. Further within CSRX 711, controlpacket data is FIFOed for presentation to and processing by SIMInterface 705, while non-control packet data is FIFOed for further datapath processing in accordance with FIG. 6D as discussed elsewhereherein.

VING 709 directs DMARX 717 to store received non-control packet data ascomplete or partially reassembled packets into Local Host Memory via DMAtransfers according to the various receive scheduling algorithms of FIG.6E. When a buffer is completely filled (or the last datum of a last cellof a packet is stored), VING 709 directs writing a correspondingcompletion queue entry, including status (Error or OK), thread number,context key, and optionally packet-level CRC and 1's complement results.This completes the reception of the packet (if the last cell wasreceived) and the packet image is available for use directly by theDriver (or optionally an Application) process executing on a LocalProcessor.

Control packets are sent in-order to SIM Interface 705 for furtherprocessing. SIM Interface 705 parses the control packet and passescommand, address, and data information to the appropriate VIOC elementfor execution. Return handshake status and result information istypically provided via ingress-egress coupling 772 as a packet(typically addressed to an SCM) for transmission to Fabric Coupling 732.Control packets, typically provided from a controlplane processexecuting on Primary SCM 140A, may be used at any time to effect updatesor changes to forwarding, VLAN, multicast, and other related stateinformation included in TCAM/SRAM coupled to VIOC 301.

Egress and ingress buffer operation is not restricted to physicaladdresses, as virtual addresses may be supplied in transmit and receivedescriptors. VIOC 301 references coupled DDR DRAM via coupling 721 toaccess translation mapping information. The VIOC then translates thevirtual addresses to physical addresses and processing proceedsaccordingly.

During message operation, Message State Machine 707 manages variousaspects of the reliable connection-oriented protocol, and directsoverall processing according to message related queues and associateddescriptors. The reliable protocol includes handshake and retryinformation that is communicated from VING 709 to VEGR 708 viaingress-egress coupling 772 for communication as messages on FabricCoupling 732. Message operation is otherwise similar to packetoperation.

Some embodiments implement packet operation only, while otherembodiments implement packet and message operation. Embodimentsimplementing only packet operation omit Message State Machine 707 andassociated processing logic.

Those of ordinary skill in the art will recognize that VIOC 301 is anexample embodiment only. For example, consider that in other embodimentsthe external couplings may have differing bandwidths to that describedheretofore. For example, a VIOC used in a controlplane context, such asan SCM included on a SIM, may be implemented with reduced bandwidthvariations of Fabric Coupling 732 and HT Channel coupling 722 comparedto a VIOC used in a dataplane context, such as a PMM. In one embodiment,the VIOC included in the SCM is coupled to the SFM via one-half thecoupling bandwidth of the VIOC included in the PMM. In anotherembodiment, the VIOC included in the OLB is coupled to the SFM viaone-half the coupling bandwidth of the VIOC included in the PMM.

Those of ordinary skill in the art will also recognize that thepartitioning illustrated in VIOC 301 is only illustrative, and that anynumber of other arrangements and variations may be implemented. Forexample, the functions relating to SIM Interface 705, VIOC Configurationblock 706, and Message State Machine 707, may be incorporated within thecontrol state machines of VEGR 708 and VING 709. Functions implementedin the blocks of FICTX 714 and FICRX 715 may be rearranged in otherequivalent organizations. These and other such arrangements arecontemplated in various embodiments.

VIOC Egress Operation

FIG. 7B illustrates selected aspects of egress operation of anembodiment of a VIOC as flow diagram Egress Overview 700B. For clarity,only selected details related to packet processing are shown (messageprocessing is similar). Processing begins upon receipt of “DoorbellRing” 781, indicating availability of one or more new transmitdescriptors pointing to packets available for transmission. Flowproceeds to “Descriptor Fetch” 780.1, where transmit descriptors arefetched (in accordance with the scheduling illustrated by FIG. 6B) andpassed to “Valid?” 780.2 to determine which descriptors are valid forprocessing by the VIOC. If an invalid descriptor is detected, then anerror condition is present, and processing is complete (“No” 780.2Nproceeds to “End” 780.14). If the descriptor is valid, then flowcontinues to “Program DMATX Transmit Q Fetch” 780.4 via “Yes” 780.2Y.

Processing continues as “Program DMATX Transmit Q Fetch” 780.4 analyzesthe fetched descriptor information to determine the buffer address andlength, and configures DMATX 716 to fetch the packet data located in thebuffer and to store the data into ESMem 736. The fetched packet data isin turn analyzed to determine the destination, and a lookup is performedaccording to the MAC destination address (MACDA) and the VLAN of theassociated with the descriptor at “Lookup” 780.5. The lookup result,including a destination fabric port address is used in part by “FormPacket Header” 780.6 to formulate a working image of a packet header.Typically the packet header includes other information from the addressblock of the VNIC sourcing the transmission (such as Address Block601.1, of FIG. 6A), including a MAC source address (such as MAC Address603.1, of FIG. 6A), and a VLAN tag (such as VLAN Identifier 617.1, ofFIG. 6A). Some embodiments implement VLAN processing such as droppingthe packet if source and destination VLANs are different.

Processing continues as “Scheduled?” 780.7 determines if a first cell ofthe packet is scheduled, and if not, loops back via “No” 780.7N untilthe cell is scheduled. The scheduling is as illustrated in FIG. 6C. Whenthe cell is scheduled (“Yes” 780.7Y), flow proceeds to “Program DMATXOutput Q Fetch” 780.8 where DMATX 716 is programmed to fetch data fromESMem 736 for insertion into the appropriate output queue. In oneembodiment, the output queues are implemented within ESMem 736. It willbe understood that data transfers within the same memory structure maybe at least in part performed logically via pointer manipulation ratherthan via physical data transfers. A cell header is formulated in “FormCell Header” 780.8A, for encapsulating cells corresponding to thepacket. The fetched data is processed (“Compute Checksum, CRC” 780.8B)to determine packet-level error detection information in CSTX 710 (ofFIG. 7A). The cell header and cell data (corresponding to cell-sizedchunks of the packet data) are then ready for transmission on the fabricby CSTX 710 (“Transmit Cells” 780.9).

Processing continues as “Packet Complete?” 780.10 determines if theentire packet has been transmitted. If not (“No” 780.10N), then flowreturns to “Scheduled?” 780.7 to continue sending the packet. If theentire packet has been transmitted (“Yes” 780.10Y), then flow proceedsto “Modify Transmit Q Descriptor” 780.11 to indicate that the bufferidentified by the transmit descriptor has been transmitted by settingthe done indicator accordingly.

Processing continues as “Interrupt Requested?” 780.12 determines if aninterrupt to the Local Processor is requested, based in part on aninterrupt request indicator included in the transmit descriptor, in oneembodiment. If an interrupt is requested (“Yes” 780.12Y), then flowcontinues to request an interrupt (“Interrupt” 780.13) and thenprocessing of the information related to the descriptor is complete(“End” 780.14). If an interrupt is not requested (“No” 780.12N), thenprocessing is complete (“End” 780.14).

The processing illustrated in Egress Overview 700B is representative ofthe overall flow with respect to one cell, including any specialprocessing relating to completion of a packet. However, according tovarious embodiments, such processing may be wholly or partiallyoverlapped for a plurality of cells. For example, in some embodimentsDescriptor Fetch 780.1 may provide a plurality of descriptors, eachpointing to a plurality of cells, and each of the respective cells areprocessed according to the remainder of the flow. In other embodiments,a first cell may remain in ESMem 736 indefinitely once processed byProgram DMATX Transmit Q Fetch 780.4, while subsequent cells areprocessed according to Program DMATX Transmit Q Fetch 780.4. Inaddition, cells may be removed from ESMem 736 in a different order thanstored, according to Program DMATX Output Q Fetch 780.8. These and allother such variations are contemplated in various embodiments.

VIOC Ingress Operation

FIG. 7C illustrates selected aspects of ingress operation of anembodiment of a VIOC as flow diagram Ingress Overview 700C. For clarity,only selected details related to packet processing are shown (messageprocessing is similar and is omitted). Processing begins when a cell isreceived from the fabric and enqueued (according to prioritiesillustrated by FIG. 6D) by CSRX 711, as indicated by “Cell Received”791. Flow continues to “Check Parities, CRC” 790.1, where cell-levelerror check computations are performed. The error results are checked(“Data OK?” 790.2), and if the data is incorrect (“No” 790.2N), then theerror is recorded (“Log Error” 790.3) and processing for the cell iscomplete (“End” 790.16). If the data is correct (“Yes” 790.2Y), thenprocessing proceeds to “UC/MC?” 790.4.

Processing continues as “UC/MC?” 790.4 determines if the cell is amulticast (“MC” 790.4M) or a unicast (“UC” 790.4U) type cell. Unicastprocessing continues at “Enque By VNIC/Q” 790.5, where the received cellis enqueued in a selected unicast receive queue according to VNIC numberand receive priority (or queue). Multicast processing continues at“Lookup” 790.17, where a lookup is performed by LE 703 (of FIG. 7A)based at least in part on the MGID as discussed elsewhere herein inconjunction with FIG. 8B. The lookup provides information describing theVNICs to receive the multicast data, and the cell is enqueuedaccordingly (“Enqueue Multicast” 790.18). Some embodiments implementselected VLAN processing such as dropping the cell if the learning VLANis different from the destination VLAN. In one embodiment, the receivequeues are implemented within ISMem 738.

Unicast and multicast processing continue at “Descriptor Fetched?”790.6, where a determination is made as to whether a receive descriptorappropriate for the cell received has been fetched. If not (“No”790.6N), then a descriptor is fetched by RXDmgr 766 (of FIG. 7A) in“Fetch Descriptor” 790.7 and examined for validity (“Fetch OK?” 790.7A).If the fetched descriptor is invalid, or no descriptors are available,then the cell is dropped (i.e. not received) along flow “No” 790.7N. Thepacket that the cell is part of is also dropped (“Drop Packet” 790.7B),and processing is complete at “End” 790.16. If the fetched descriptor isvalid, then flow proceeds (“Yes” 790.7Y) for receive scheduling at“Scheduled?” 790.8. If an appropriate receive descriptor is alreadyavailable (“Yes” 790.6Y), then processing also continues at “Scheduled?”790.8.

Processing in “Scheduled?” 790.8 determines if the cell has beenscheduled (according to priorities illustrated in FIG. 6E), and if not(“No” 790.8N), then processing loops back. If the cell has beenscheduled (“Yes” 790.8Y), then processing continues at “Program DMARXDeQueue Fetch” 790.9, where DMARX 717 (of FIG. 7A) is programmed tofetch the cell data from the shared ingress memory and to store the celldata into local host memory according to the fetched receive descriptor.Error checking information is then computed (“Compute Checksum, CRC”790.10), and for multicast cells a check is made to determine ifmulticast replication is complete (“MC Finished?” 790.11). If multicastprocessing is not complete (“No” 790.11N), then processing returns to“Scheduled?” 790.8 to await subsequent scheduling of the next multicastoperation. If multicast processing is complete (or the cell is a unicastcell), then flow continues along “Yes” 790.11Y to “EOP?” 790.111. If thecell is not an End Of Packet (EOP) cell and there is room available forstorage of additional cell data (according to the fetched receivedescriptor), then processing for the cell is complete (“End” 790.16).Otherwise, flow proceeds to “Write Completion Q Descriptor” 790.12 torecord completion of the receive descriptor. In alternate embodiments,processing for multicast cells is performed wholly or partially inparallel, including embodiments where all multicast destinations for thecell are processed in parallel.

Processing in “Write Completion Q Descriptor” 790.12 records completionof the processing of the receive descriptor, or consumption of thedescriptor, by entering an entry on a designated write complete queue.The entry includes packet and error status. Then a determination is made(“Interrupt>Threshold ?” 790.13) as to whether the number of receiveevents exceeds a specified threshold. If so (“Yes” 790.13Y), then aninterrupt is signaled to the Local Processor (“Interrupt” 790.14). Ifthe threshold has not been reached (“No” 790.13N), then a furtherdetermination is made if a timer has expired (“Timer Expired?” 790.15).If so (“Yes” 790.15Y), then an interrupt request is sent to the LocalProcessor (“Interrupt” 790.14), and then processing for the cell iscomplete (“End” 780.14). If not (“No” 790.15N), then processing for thecell is immediately complete (“End” 780.14).

The processing illustrated in Ingress Overview 700C is representative ofthe overall flow with respect to one cell, including any requiredmulticast processing and special processing relating to an EOP cell orconsumption of a receive descriptor. However, according to variousembodiments, such processing may be wholly or partially overlapped for aplurality of cells. For example, once a first cell has been processedaccording to “Enque By VNIC/Q” 790.5, processing for the first cell maybe suspended indefinitely, and in the meantime a plurality of additionalcells may be received and processed up to and including “Enque ByVNIC/Q” 790.5. In addition, cells may be processed according to “ProgramDMARX DeQueue Fetch” 790.9 in a different order than processed accordingto “Enque By VNIC/Q” 790.5. As another example, “Scheduled?” 790.8 isconceptually performed for many (for example all) enqueued cells onevery cycle, even though only a subset of cells is scheduled accordingto “Yes” 790.8Y (for example, only a single cell may be scheduled). Insome embodiments, ISMem 738 is used to store received cells during someportion of the processing time corresponding to “Enque By VNIC/Q” 790.5through “Yes” 790.8Y. As another example of overlapped processing,processing of a first cell according to “Lookup” 790.17 may be wholly orpartially concurrent with processing of a second cell according to“Check Parities, CRC” 790.1. These and all other such similar variationsare contemplated in various embodiments.

In some embodiments, packets are aligned on cache line boundaries, andpackets are segmented along cache line boundaries into cells. Inembodiments where local host memory may be referenced a cache line at atime, there is a one-to-one correspondence between local host memorycache line references and cells. For example, during egress processing,reading the first cache line of the packet provides data correspondingentirely to the first cell. Reading the second cache line provides dataentirely for the second cell, and so forth. During ingress processing,reception of the first cell of the packet provides a full cache line ofdata that is also aligned with respect to the receiving buffer, and theentire received cell may be written to the local host memory in a singletransaction. Subsequently received cells may also be written one cellper cache line transaction.

In some embodiments, packet-level error detection information iscomputed, transmitted, and checked upon reception irrespective of packetsize. In other embodiments, if all of the data for a packet fits in asingle cell, then no packet-level error detection information iscomputed or transmitted, enabling the transmission of additional databytes instead of the error detection information. For example, if atwo-byte CRC is used for error detection, then two additional data bytesmay be sent instead of the CRC. In these circumstances the cell errordetection information (such as a CRC) provides error detectioninformation for the packet.

Those of ordinary skill in the art will recognize that the processingillustrated by the aforementioned flow diagrams is illustrative ofcertain embodiments, and that other embodiments are also possible. Forexample, operations may be partitioned or ordered differently, orselected aspects of processing may be altered. These and all otherrelated variations are contemplated.

TCAM/SRAM Lookup State

In their most general form, TCAM lookups may be performed using acombination of “local” and “global” masks. Each entry in the Tag arraylogically has a data field (holding a data value) and an associatedequal width local mask field (holding a local mask value). Equivalently(and possibly physically), the Tag array may also be described as havinga data array and a corresponding mask array. Also provided are one ormore global mask registers (holding a global mask value of the samewidth as the data and local mask values) located outside the Tag array.In parallel for all entries in the Tag array, the data value of eachentry has applied to it the associated local mask value of the entry anda selected global mask value. The masked data value is then comparedagainst the search key. One or more entries in the Tag array may resultin a hit (a match with the key). A priority-encoder selects the highestpriority entry (the match at the lowest address), which is used as anindex to address the SRAM and retrieve the corresponding result entry.

The mask values that will be used for a search are often known well inadvance and are often stable for extended periods of operation.Accordingly, many mask values (in the local mask array and the globalmask registers) may be programmed well in advance of the search. Thispermits the searches to proceed more quickly.

Generally, local mask values are required at least in part if the use ofsimultaneous prioritized hits to more than one entry is desired.Specifically, in some broadcast embodiments, the use of local maskvalues is used to establish an arbitrary-MACDA low-priority broadcastentry for each VLAN. For the broadcast TCAM entry, the data valueincludes the VLANid for the VLAN and a null MACDA, and the MACDA-relatedbits of the local mask are cleared to prevent the null MACDA field fromparticipating in comparison with presented keys. If there are no otherentries in the TCAM to match on the VLANid, then the multicast result(and included MGID) corresponding to the broadcast entry will bereturned. The broadcast entry is used to flood the frame being forwardedto all members of the VLAN. In some addressing embodiments, this isaccomplished by providing a multicast result that includes a MulticastGroup ID (MGID) that has been assigned to the VLAN. When a MACDA on aVLAN is learned, a higher-priority (lower addressed) MACDA-specificnon-broadcast entry is created wherein the data value generally includesthe VLANid for the VLAN and the learned MACDA, and the MACDA-relatedbits of the local mask are set to enable the MACDA field to participatein the comparison with presented keys. Subsequent searches using a keyhaving both the VLANid and the MACDA will cause hits to both thenon-broadcast and broadcast entries. Since the broadcast entry iscreated at a higher address, the TCAM's priority encoder only returnsthe MACDA-specific non-broadcast entry.

The following TCAM illustrations are intentionally general to encompassa number of implementation options and variations. For example, the useof both local and global masks is allowed for as are TCAM Tag-entry andSRAM result-entry organizations that support both IVL and SVL modes ofoperation. The combination of local and global masks is illustrative andnot limiting. Within a given implementation, either local masks orglobal masks could be eliminated with an associated reduction in thelogic associated with the eliminated functionality. (However,elimination of local masks generally requires performing a subsequentbroadcast lookup upon encountering a previously unlearned MACDA.)Likewise, the combination of IVL and SVL is merely illustrative and notlimiting. One of either IVL or SVL could be eliminated with possiblyassociated reductions in certain fields within the TCAM Tag-entries andSRAM result-entries.

It will be understood that some operations could be carried outequivalently (although generally not as quickly) through use of justindividual local mask values or just global mask values, and likewisecould be carried out through values formulated at the time of the search(and stored into either a global mask register or the local mask array).In particular, the selective masking of the VLANid field within the TCAMTag array to selectively implement one of the IVL and SVL modes ofoperation could be done through use of a global mask value or throughuse of the local mask values. Whether operations are based upon the useof local mask values, the use of global mask values, or some combinationof local and global masks, and whether a given mask value ispre-programmed or formulated and programmed at the time of the search,will be based upon designer preference and situational specifics in amanner that is understood to those of ordinary skill in the art.

The following TCAM illustrations are also described in terms of a singleoverall TCAM/SRAM combination. It will be understood that the overallTCAM/SRAM may be physically implemented using a plurality of smallerTCAM/SRAM primitives (i.e., smaller in entry-width, number of entries,or both) arranged in ways known to those of ordinary skill in the art toprovide the desired number of entries and entry-width of the overallTCAM/SRAM.

As previously described with respect to egress operation, “Lookup” 780.5(see FIG. 7B) includes a lookup in a TCAM/SRAM coupled to a VIOC (suchas VIOC 301.5 coupled to TCAM/SRAM 403.5), as performed by LE 703.Similarly, with respect to ingress operation, “Lookup” 790.17 (see FIG.7C) includes a lookup in the TCAM/SRAM. The lookup operations areperformed by formulating a lookup key, optionally selecting a globalmask register, and presenting the key and optional global mask value tothe TCAM portion of the TCAM/SRAM. A result is then produced by readingthe first matching entry (if any) as determined by the TCAM from theSRAM portion of the TCAM/SRAM. The TCAM/SRAM is programmed according tovarious provisioning, switching, and routing functions, as describedelsewhere herein.

Egress TCAM/SRAM keys, masks, and results are formulated to provide fortransparent processing of various L2 switching related activities, andselected L3 switching and routing related activities. The L2 and L3operations include multicast and unicast, with and without LinkAggregation Group (LAG) processing, and further include VLAN processing.A lookup key is formed without specific knowledge concerning thedestination, other than the MAC Destination Address (MACDA). In otherwords, the key is formed in the same manner for multicast and unicastdestinations. As described in more detail below, the lookup resultprovides information specifying the type of destination (multicast,unicast, or unicast LAG), along with information specific to thedestination according to the destination type.

FIG. 8A illustrates selected aspects of an embodiment of an egresslookup key and result entries as TCAM/SRAM Egress Layout 800A. Theegress layout is an example of a portion of a MAC Forwarding InformationBase (MACFIB) implementation. A 64-bit lookup key, Egress Key 801, hasseveral fields, including: Egress PathID 899A (two bits), Egress TableID898A (two bits), VLANid 805 (12 bits), and MACDA 806 (48 bits). Invarious embodiments, the PathID is 0x0 and the TableID is 0x0.

Embodiments implementing IVL formulate lookup keys including the VLANidassociated with the source (such as a VNIC or NM port), such as VLANIdentifier 617.1 or a value derived from it, according to embodiment. Ifthe VLANid and the MACDA of the key match to a TCAM entry having boththe same VLANid and the same MACDA as the key, then a non-broadcast(unicast or multicast) entry has been identified and the correspondingSRAM result is retrieved.

In a first SVL embodiment, lookup keys and TCAM data array values areformed with a common predetermined value (such as all zeros) in theVLANid field of the key and in the corresponding VLANid field of theTCAM entries. Since the TCAM entries so programmed always match on thecommon predetermined VLANid, forwarding entries learned for one VLAN areaccessible by other VLANs. If no entry matches on the commonpredetermined VLANid, then the MACDA has yet to be learned, and somesubsequent means must be used to broadcast over the VLAN. The previouslydiscussed catch-all broadcast entry (wherein the MACDA field is masked)could still be used, being looked-up using a key with the VLANid of thesource VLAN in a follow-up TCAM search.

A second SVL embodiment uses two global mask registers. In a firstsearch, lookup keys are formed with the MACDA specified by the source,but with arbitrary values in the VLANid portion of the key. In a firstglobal mask register, mask bit locations corresponding to the VLANidbits are cleared to remove the VLANid bits of the data array fromparticipation in the TCAM search, while mask bit locations correspondingthe MACDA bits are set to ensure their participation in the search. As aresult, for previously learned MACDAs, TCAM entries match on the MACDAof the key regardless of the VLANid of the key, and forwarding entrieslearned for one VLAN are accessible by other VLANs. If no entry matches,then the MACDA has yet to be learned. In order to broadcast over theVLAN of the source, a second lookup is performed, this time with a keyhaving the VLANid of the source and arbitrary values in the MACDAportion of the key. In the second lookup, a second global mask registeris used, this time having the mask bit locations corresponding to theVLANid set and the mask bit locations corresponding to the MACDA bitscleared. In the second SVL embodiment, the VLANid field is not strictlyrequired in the lookup key for SVL-only implementations. However, if theVLANid field is not present in the TCAM, then in order to implementbroadcast when the MACDA is yet to be learned by the TCAM, the VLANid tobroadcast address mapping must be resolved using other logic.

A third SVL embodiment uses local masks. For non-broadcast entries, themask bit locations in the local mask array corresponding to the VLANidfield are cleared to remove the VLANid bits of the data array fromparticipation in the TCAM search (the mask bit locations in the localmask array corresponding to the MACDA field are set). As before, forpreviously learned MACDAs, TCAM entries match on the MACDA of the keyregardless of the VLANid of the key, and forwarding entries learned forone VLAN are accessible by other VLANs. A broadcast entry as describedabove, which reverses the local masking between the VLANid field and theMACDA field, would within the same lookup still provide the broadcastmatch if the MACDA has yet to be learned.

The MACDA is a value provided in the packet (or message) header includedin the buffer image formed in the Local Processor Memory, or the MACDAis derived in part from the header. Since the destination may be one ofseveral types, the format of the 64-bit result returned variesaccordingly, including: multicast, unicast, and unicast LAG formats, asillustrated by Multicast Result 802, Unicast Result 803, and Unicast(LAG) Result 804, respectively.

Multicast Result 802 has several fields, including: Multicast Bit(Multicast) 807.M (one bit), VLANid (Multicast) 808.M (12 bits), andEgress MGID 809 (16 bits). The multicast bit is asserted if the resultcorresponds to a multicast destination, and deasserted otherwise. Asthis is a multicast result, the multicast bit is asserted. The VLANididentifies the VLAN membership of the destination. The MGID identifiesthe destination multicast group, and may be associated with a VLANbroadcast group or an IP broadcast group. Subsequent processing uses theMGID to replicate information to one or more destinations, as determinedby the identified multicast group.

Under SVL, in order to enforce inter-VLAN isolation, if the destinationVLAN identifier does not match the source VLAN identifier, then theegress data is discarded. The VLANid field is not strictly required inthe multicast, unicast, or LAG results of IVL-only implementations.Under IVL, TCAM matches (and subsequent result retrievals) arepredicated upon the destination residing within the VLAN of the source,thus checking the VLANid field of the result is superfluous.

Unicast Result 803 has several fields, including: Multicast Bit(Unicast) 807.0 (one bit), LAG Bit (Unicast) 810.0 (one bit), VLANid(Unicast) 808.0 (12 bits), DstFabAddr 811 (eight bits), DstSubAddr 812(four bits), Egress DstQ 813 (four bits), and DstLFIFID (Unicast) 814.0(12 bits). The multicast bit is deasserted to indicate the result is aunicast result. The LAG bit is deasserted to indicate the result is nota LAG result. VLANid (Unicast) 808.0 is identical in format and functionto VLANid (Multicast) 808.M.

DstFabAddr 811 identifies the destination fabric port address (typicallyassociated with a slot having an inserted pluggable module). DstSubAddr812 identifies a sub-address distinguishing one of a plurality ofsub-destinations associated with the destination fabric port address. Inembodiments including a VIOC implementing VNICs, DstSubAddr 812typically identifies either a) one of the plurality of VNICs implementedin the VIOC at the destination, or b) one of the plurality of networkports of a multi-ported NM. DstQ 813 typically identifies a packetreceive queue associated with the identified VNIC.

Certain L3 processing operations (such as port filtering) areimplemented in some embodiments according to DeSTination LogicalInterFace IDentifers (DstLIFIDs). DstLIFIDs are typically global, andmay be used by software or hardware components (such as NMs), accordingto embodiment. DstLIFID (Unicast) 814.0 is a DstLIFID associated withthe destination identified by MACDA 806.

Unicast (LAG) Result 804 has several fields, including: Multicast Bit(LAG) 807.UL (one bit), LAG Bit (LAG) 810.UL (one bit), VLANid (LAG)808.UL (12 bits), LagID 815 (eight bits), and DstLIFID (LAG) 814.UL (16bits). The multicast bit is deasserted to indicate the result is aunicast result. The LAG bit is asserted to indicate the result is a LAGresult. VLANid (LAG) 808.UL is identical in format and function toVLANid (Multicast) 808.M. LagID 815 identifies the LAG the destinationis associated with to enable load balancing, failover, and other relatedoperations with respect to the identified LAG. DstLIFID (LAG) 814.UL isidentical in format and function to DstLIFID (Unicast) 814.U.

Subsequent processing of Unicast Result 803 and Unicast (LAG) Result 804provides portions of the lookup result, or information derived in partfrom the lookup result, for use in forming selected egress cell headers.For example, various combinations of DstFabAddr 811, DstSubAddr 812,Egress DstQ 813, and DstLIFID (Unicast) 814.0 (or data derived fromthem, according to embodiment) are included in selected cell headersformulated during data transmission, according to embodiment. Similarly,various combinations of LagID 815 and DstLIFID (LAG) 814.UL (or dataderived from them, according to embodiment) are included in selectedcell headers during data transmission, according to embodiment.

Providing destination information such as the destination fabric portaddress, sub-address (or VNIC identifier), destination queue, anddestination logical interface in the lookup result enables transparentL2 and selected L3 operations with respect to processes sending data.The sending processes address data by MACDA, and are not aware ofmulticast, unicast, and LAG properties associated with the destination.The lookup destination information further enables transparentmanagement of bandwidth and other related resources by agents other thanthe Local Processor process sending the data. Such agents includemanagement, controlplane, and load balancing processes executingelsewhere.

FIG. 8B illustrates selected aspects of an embodiment of an ingresslookup key and result entry, as TCAM/SRAM Ingress Layout 800B. Theillustrated ingress layout embodiment is an example of an implementationof an MGID table. A 64-bit lookup key, Ingress Key 821, has severalfields, including: Ingress PathID 899B (two bits), Ingress TableID 898B(two bits), Ingress Mask 823 (44 bits), Multicast Key Bit 897 (one bit),and Ingress MGID 824 (15 bits). In various embodiments, the PathID is0x1 and the TableID is 0x0.

To enable use of the same TCAM on ingress and egress, the same size keyis used for both ingress and egress searches. At a physical level theTCAM operates identically for ingress and egress searches, comparingeach presented key in parallel with all of the stored data values asmasked by the local mask values and the global mask value, as describedpreviously. As discussed in further detail below, the PathID and TableIDbits are commonly laid out between the ingress and egress entries. Thesebits participate in the TCAM comparisons, allowing if so desired theingress and egress entries, and entries from multiple tables, to beco-mingled in the TCAM while remaining logically distinct subsets.Beyond the PathID and TableID bits, ingress searches only require the 16bits corresponding to the Ingress MGID 824 bits and the Multicast KeyBit 897. Multicast Key Bit 897 is asserted to indicate the lookup is amulticast type search. Ingress MGID 824 is directly from an MGID fieldincluded in the received cell header, or is derived from the header,according to embodiment.

The remaining 44 bit positions of the common key layout, denoted byIngress Mask 823, are null place-holders, being neither required norlogically used on ingress lookups. In a first ingress embodiment, foreach ingress entry, the mask bit locations within the local mask arraycorresponding to Ingress Mask 823 are cleared to insure that the bitlocations within the data array corresponding to Ingress Mask 823 do notparticipate in ingress searches. In a second ingress embodiment, thecorresponding mask bits within a global mask register are cleared toaccomplish the same result.

Ingress Result 822 is 64 bits and has several fields, including: IngressDstQ 825 (four bits) and VNIC BitMask 826 (16 bits). In someembodiments, Ingress DstQ 825 identifies one of a plurality of multicastpacket receive queues for insertion of the received data into (see thediscussion relating to FIG. 6D). In embodiments including a VIOCimplementing VNICs, VNIC BitMask 826 identifies destination VNICs forreplication of the received data. Typically there is a one-to-onecorrespondence between asserted bits in VNIC BitMask 826 and VNICs thatare to receive the multicast data.

Egress PathID 899A and Ingress PathID 899B are arranged to be in thesame location in the egress and ingress lookup keys, respectively. Anegress path lookup is identified by the value 0x0 and an ingress pathlookup is identified by the value 0x1, thus enabling selectedembodiments to include egress and ingress lookup information in a sharedTCAM/SRAM (such as TCAM/SRAM 403.4). Other embodiments may provideseparate TCAM/SRAM resources for egress and ingress processing. EgressTableID 898A and Ingress TableID 898B are in the same location and maybe used to specify one of a plurality of tables to facilitate additionallookup information for use in other scenarios.

Those of ordinary skill in the art will recognize that the egress andingress key and result layouts described are example embodiments only,and that there are any number of possible arrangements of keys andresults that provide similar information. For example, the widths andencodings of fields may vary, selected fields may be omitted, andadditional fields may be added.

Server Provisioning and Management

An ES system provides one or more provisioned servers in conjunctionwith a provisioned L2/L3 switch and associated network topology. Each ofthe provisioned servers and the provisioned switch and network includecapabilities as identified by a corresponding set of specifications andattributes, according to various embodiments. Typically thespecifications (or constraints) and attributes are specified with an SCF(see the SCF and Related Tasks section, elsewhere herein).

An ES system may be provisioned into a wide-range of server combinationsaccording to needed processing and I/O capabilities. For example,servers may be provisioned according to various illustrative applicationusage scenarios described elsewhere herein including: a Unix server, anI/O intensive server, a data-center tier-consolidation server, and anenhanced high availability server. Each of these servers may includedistinct compute, storage, and networking performance Provisionedservers may be managed similar to conventional servers, includingoperations such as booting and shutting down (see the server operationalstates section, elsewhere herein).

An ES system may also be provisioned to configure a wide range ofnetworking capabilities and logical switch topologies within the ESsystem (i.e., internal to the chassis of the ES system). For example,the networking may be provisioned such that a logical L2/L3 switchprovides L2 and L3 forwarding for VNICs of provisioned servers withinthe ES system and other network interfaces external to the ES system.Any of the logical ports of the L2/L3 switch may be configured to bepart of a VLAN and multiple simultaneous VLANs are possible. Aprovisioned server may optionally be provided with a dedicated (a.k.a.“pinned”) network port for direct non-switched coupling to an externalnetwork. Another option is the implementation one or more LAGs, wheremultiple physical network ports are aggregated to form one logical portof the L2/L3 switch.

FIG. 9A illustrates a Hardware Resources View 900A of an embodiment ofan ES system. Provisioned servers and an associated network and switchcomplex are formed by assigning hardware resources from a collection ofavailable hardware resources (such as any or all of the elements ofHardware Resources View 900A) and then programming configuration andmanagement state associated with the assigned hardware resources. FIG.9B illustrates a Provisioned Servers and Switch View 900B of anembodiment of an ES system, and conceptually represents the result ofprovisioning several servers and network functionality from the hardwareelements of Hardware Resources View 900A.

More specifically, Hardware Resources View 900A illustrates oneembodiment having a Primary SFM 180A, a Primary SCM 140A, a first NM130A, a second NM 130B, a first PMM 150A, and a second PMM 150B. NM 130Aand NM 130B each provide a plurality of network ports for interfacingwith networks external to the ES system and further adapts those portsto couple with the cell-based Primary SFM 180A. As illustrated, theports of NM 130A are coupled to the Internet 910 while the ports of NM130B are coupled to Data Center Network 920. It will be understood thatthis configuration is merely illustrative and the ES system may beconfigured for use with a wide range of external network topologies.Each NM has an associated fabric address on the Primary SFM 180A andeach network port of the NMs has an associated fabric sub-address.

Each PMM has two 2-way SMP Processing Complexes that can be optionallycoupled (via configurable couplings 990A and 990B respectively) as asingle 4-way SMP Processing Complex. (Each of couplings 990A and 990Brepresents coupling pair 460.5X and 460.5Y of FIG. 4B.) Additionally,couplings 179A and 179B may be configured in conjunction with CSFI 170to couple the two PMMs together as a single 8-way SMP ProcessingComplex. In an illustrative scenario, 2-way and 4-way configurationshave been chosen and thus couplings 179A and 179B are configured asinactive (as suggested by dashed lines, rather than solid lines). PMM150A is configured such that coupling 990A is not active (as suggestedby dashed lines), facilitating the formation of 2-way SMP ProcessingComplex 901.2 and 2-way SMP Processing Complex 901.1. PMM 150B isconfigured such that coupling 990B is active (as suggested by solidlines), facilitating the formation of 4-way SMP Processing Complex901.0. It will be understood that since the two PMMs are physicallyidentical, the illustrated scenario is an arbitrary choice. Both PMMscan just as easily be configured in any combination of 2-way and 4-waySMP Processing Complexes (up to four 2-ways, one 4-way and up to two2-ways, up to two 4-ways, or one 8-way). In this way, the ES systemprovides for an easily scalable number of SMP processor-ways from whichto configure physical partitions, which are the basis for provisionedservers.

Each 2-way SMP Processing Complex is associated with a VIOC that adaptsthe Complex to the cell-based Primary SFM 180A. While in FIG. 9A eachVIOC is represented by only one VNIC, in one illustrative embodimenteach VIOC includes 16 VNICs. Each VIOC has an associated fabric addresson the Primary SFM 180A and each VNIC has an associated fabricsub-address. In conjunction with appropriate device drivers, each VNICappears to the operating software on the SMP Complex as ahigh-performance Ethernet compatible NIC. Each VNIC can be selectivelyenabled, thus any subset of the 16 VNICs may be provisioned for use bythe associated 2-way SMP Processing Complex. In this way, the ES systemprovides easily scalable virtualized I/O services to the provisionedservers. In one embodiment, 2-way, 4-way, and 8-way physical partitionsare envisioned that make use of the 2-way SMP Processing Complex andit's associated VIOC and VINCs as an underlying primitive. Accordingly,each of up to four 2-way physical partitions consists of a 2-way SMPProcessing Complex and up to 16 VNICs, each of up to two 4-way physicalpartitions consists of two coupled 2-way SMP Processing Complexes and upto 32 VINCs (up to 16 VNICS in each of two groups), and an 8-wayphysical partition consists of four coupled 2-way SMP ProcessingComplexes and up to 64 VNICs (up to 16 VNICs in each of four groups). Asillustrated, physical partition P₁ 201 consists of 2-way SMP ProcessingComplex 901.2 and VNIC 154A.1, physical partition P₂ 202 consists of2-way SMP Processing Complex 901.1 and VNIC 154A′.1, and physicalpartition P₃ 203 consists of 4-way SMP Processing Complex 901.0 andVNICs 154B.1 and 154B′.1.

The fabric infrastructure of FIG. 9A is not seen by the softwareoperating on the SMP Complexes or by external sub-systems. Theseentities need not be concerned with (and in fact are isolated from)knowledge about the fabric addresses and fabric sub-addresses. Softwareand external sub-systems operate conventionally, communicating throughpackets and messages over Ethernet frames using either Ethernet-styleMACDAs or IP addressing. The SCM 140A maintains separate master L2 andL3 FIBs (an L2 FIB and a separate L3 FIB). The L2 FIB mapsEthernet-style MACDAs to fabric addresses and sub-addresses and the L3FIB maps destination IP addresses to fabric addresses and sub-addresses.The L2 and L3 FIBs are initialized and updated with mappings for theprovisioned hardware resources internal to the ES system and othermappings are learned over time based on network traffic processed.

Each NM and VIOC makes L2 forwarding decisions for packets they receive(via the network ports of the NM and via the SMP Complex associated witheach VIOC) by referencing a local copy of the L2 FIB. That is, each NMand VIOC does a local L2 FIB lookup on the MACDA of each packet received(packets heading toward the SFM) and determines the fabric address andsub-address within the ES system where the packet should be delivered.The NM or VIOC then provides a fabric-addressed cellified version of thepacket to the Primary SFM 180A, which delivers the cellified packet tothe module specified by the fabric address (PMM 150A, PMM 150B, NM 130A,or NM 130B). In turn, each module delivers the reconstructed packet tothe network port or VNIC specified by the fabric sub-address.

As detailed elsewhere herein, for multicast packets (including packetsbroadcast on VLANs), the packets are replicated as required both priorto fabric insertion (for each fabric address in the multicast group) andafter fabric egress (for each fabric sub-address in the multicastgroup). In one embodiment, the multicast to fabric sub-address mappingis determined via multicast group lookups in the L2 FIBs.

Provisioned Servers and Switch View 900B (of FIG. 9B) illustrates threeexample resultant provisioned servers as Provisioned Server PS₂ 902.2,Provisioned Server PS₁ 902.1, and Provisioned Server PS₀ 902.0. Thesecorrespond respectively to physical partition P₁ 201, physical partitionP₂ 202, and physical partition P₃ 203, of the Hardware Resources View900A of FIG. 9A. Each provisioned server includes compute and I/Oresources. For example, Provisioned Server PS₁ 902.1 includes 2-way SMPProcessing Complex 901.1 and network connectivity via NIC Function903.1. Provisioned Server PS₀ 902.0 includes 4-way SMP ProcessingComplex 901.0 and network connectivity via NIC Function 903.0A and NICFunction 903.0B.

In accordance with the above described L2 forwarding decisionfunctionality of the NMs and VIOCs, the network ports and VNICs readilylend themselves to the logical view (of FIG. 9B) that they are coupledto the ports of a L2 switch (exemplified by L2/L3 Switch 930). (While inthe hardware view of FIG. 9A, the L2 switch forwarding decisions are infact performed within the NMs and VIOCs.) Switch 930 provides selectiveisolation between the logical network segments coupled to each switchport. Switch 930 forwards packets between the switch ports (networksegments) only when warranted to reach a known MACDA on an otherwiseisolated segment (or when the MACDA is unknown and thus can only bereached via a broadcast on the otherwise isolated segments).

As illustrated, Switch 930 provides its selective isolation/forwardingfunctionality to resources both within and external to the ES system.For example, packets originating in Data Center Network 920 areselectively isolated-from/forwarded-to destinations associated withInternet 910, Provisioned Server PS₁ 902.1, and Provisioned Server PS₀902.0, as warranted by the specified MACDA. Unicast packets exchangedsolely between two end-points nodes are not observable by other nodeseither inside or outside the ES system.

VLANs are a common networking administration tool to selectively isolateor couple multiple network segments for collaboration, security, andperformance motives. A common VLAN implementation is the so-calledport-based VLAN, wherein each logical switch-port is defined to beassociated with a particular VLAN. Switch ports (and associated networksegments) belonging to the same VLAN are logically coupled forforwarding and broadcast events (they are part of the same broadcastdomain), while switch ports (and associated network segments) belongingto different VLANs are L2 isolated for all events (they are in differentbroadcast domains).

The L2 FIB lookup architecture of the ES system has integral support forport-based VLANs. In the logical view of FIG. 9B, port-based VLANs aredefined by associating each of the switch-ports of Switch 930 with aparticular VLAN. In the hardware resource view of FIG. 9A, SCM 140A hasa VLAN Manager that associates each NM port and each VNIC with aparticular VLAN.

Unless expressly identified as a member of another VLAN, each NM portand VNIC in the system is by default a member of the VLAN known asVLAN1. As illustrated in FIG. 9B, a subset of the switch-ports of Switch930 are expressly associated with VLAN 905 (a different VLAN thanVLAN1). Specifically, those switch-ports associated with interconnect937, 938, and 940, are members of VLAN 905. Switch ports and associatednetwork segments within VLAN1 are selectively coupled for forwarding andbroadcast events as warranted. Network segments (switch ports) withinVLAN 905 are similarly selectively coupled for forwarding and broadcastevents as warranted. From a strict L2 view, network segments withinVLAN1 are never coupled to network segments within VLAN 905. In effect,the two VLANs function as though each were topographically segregatedincluding having two separate switches (one for each VLAN).

Provisioned Server PS₂ 902.2 includes 2-way SMP Processing Complex 901.2and network connectivity as illustrated by (virtualized) NIC Function903.2. In an example of a special networking option, VNIC 154A.1 is“pinned” to the port of NM 130A associated with interconnect 131. Thatis, the port of NM 130A associated with interconnect 131 has beendedicated to data traffic to and from VNIC 154A.1. More specifically,data traffic coming into the dedicated network port goes only to VNIC154A.1 and data traffic coming from VNIC 154A.1 goes only to thededicated network port. This creates the logical view shown in FIG. 9B,where NIC 903.2 appears to be coupled directly to Internet 910 viainterconnect 931, without use of L2/L3 Switch 930.

As described elsewhere herein, provisioned servers may include OLB andFCM resources (not shown explicitly in FIGS. 9A and 9B). In contrast toPMMs, where granularity of allocation is typically by physical partition(such as 2-way, 4-way, or 8-way), OLB and FCM allocation granularity isby number, bandwidth capacity, and relative queuing priorities of VNICsimplemented in VIOCs included on OLBs and FCMs. A first level ofresource partitioning between provisioned servers may be accomplished byallocating appropriate numbers of VNICs to each of the provisionedservers (a greater number of VNICs generally corresponding to largerallocations). For example, a first provisioned server may be allocated asingle first VNIC of an OLB, while a second provisioned server may beallocated second, third, and fourth VNICs of the OLB. In someembodiments, VNICs implement various combinations of minimum and maximumbandwidth, providing a second level of resource control, such that thefirst VNIC may be allocated a first maximum bandwidth and the second,third, and fourth VNICs may be allocated respective second, third, andfourth maximum bandwidths. A third level of resource sharing control maybe implemented by proper variation of VNIC queuing priorities, asdescribed elsewhere herein. FCM resource partitioning may beaccomplished in the same manner, by assigning proper number, bandwidthcapacity, and relative queuing priorities of VNICs implemented by VIOCson FCMs.

Provisioned servers are logically isolated from each other. For example,each provisioned server may be characterized by a group of VNICscorresponding to resources allocated to the server. By assigning eachgroup of VNICs to distinct VLANs, at least one VLAN per server, theneach of the provisioned servers remains completely isolated form theothers, even though multiple servers may be using resources from thesame module (such as an OLB or FCM). For example, first and secondprovisioned servers may be using a shared OLB via respective first andsecond VNICs. If the first and second VNICs are assigned respectively todistinct first and second VLANs, then the provisioned servers areisolated, even though both are using the shared OLB. Similar isolationmay be provided when provisioned servers share an FCM, by associatingthe groups of VNICs to distinct VLANs.

Link Aggregation

Link aggregation provides a way to linearly scale connectivity bandwidthand also offers reliability and availability benefits. The L2 FIB lookuparchitecture of the ES system supports link aggregation. The NM 130Aports associated with interconnect 133 and 134 in FIG. 9A (interconnect933 and 934 in FIG. 9B) are aggregated to form one logical port (withdouble the bandwidth) illustrated in FIG. 9B as LAG 950. While notexpressly illustrated, link aggregation across multiple NMs is alsopossible. Load balancing processing is performed in conjunction with theL2 FIB lookup architecture to distribute the traffic quasi-evenly overthe ports that comprise the aggregate. In some embodiments, NM portsthat are aggregated must be of the same media type.

Control and Management Processes

FIG. 9C illustrates an operational view of selected aspects of varioussystem control and system management SW and processes (includingprovisioning) in an embodiment of an ES system. Many provisioningfunctions store, access, and communicate data using abstractions andrepresentations derived from the Common Information Model (CIM), asdescribed by CIM Schema v2.8.2 from http://www.dmtf.org, hereinincorporated by reference for all purposes, for example. Selectedcommand and result communications use abstractions and representationsderived from the Common Object Request Broker Architecture (CORBA), asdescribed by CORBA: Core Specification Version 3.0.3, March 2004, fromhttp://www.omg.org, herein incorporated by reference for all purposes,for example.

SW layers (Platform Manager 531, and Enterprise Manager 530, of FIG. 5B)conceptually surround HW core ES1 110A (FIG. 1A). As illustrated,Platform Manager 531 is representative of not only Platform Manager 531but also the SW modules operating in close cooperation with the PlatformManager. Such modules may include CLI 532, CM 533, Query Engine 534,Repository Manager 535, VIOC Manager 536, Interface Manager 537, L2 FDBManager 538, VLAN Manager 539, and Other Management Code 540 (see FIG.5B), according to embodiment. The SW layers execute using resourcesincluded in the HW core (such as Primary SCM 140A), and providesystem-level control and management of the HW core. Persistent staterelating to these operations is maintained in CIM-compatible formats intwo repositories, Primary CIM Instance Repository 917.P and SecondaryCIM Instance Repository 917.S. Non-volatile storage for theserepositories may be included in various elements of Flash memory,Magnetic Disk memory, and Optical Disk memory, according to embodiment,and interfaced to various elements of ES1 110A (such as SCMs, PMMs, orOLBs), or directly included in such elements, also according toembodiment. In some embodiments, the secondary repository is notspecifically stored in persistent storage, but is stored as datastructures in portions of processor main memory (such as DRAM and cachememory), although OS related paging operations may swap memory pagesincluding portions of the repository to disk. In some embodiments, thesecondary repository is not present, and accesses to the secondaryrepository are replaced with accesses to the primary repository.

Enterprise Manager 530 provides an interface for client GUIs (such asGUI 914.1 and GUI 914.2) and maintains Secondary CIM Instance Repository917.S. Platform Manager 531 provides an interface for remote shellwindow CLIs (such as CLI 911.1 and CLI 911.2), and maintains Primary CIMInstance Repository 917.P. The Enterprise and Platform Managerscooperate to keep the Primary and Secondary Repositories synchronized.Communication between Client GUIs and remote shell CLIs is generally viaCIM and CORBA standard representations, (or similar techniques), asshown by CIM Communication 1 916.1, CIM Communication 2 916.2, CORBACommunication 1 916.3, and CORBA Communication 2 916.4.

GUIs enable performance of various system management and configurationcontrol operations by system management personnel, including variousaspects of HW and SW operation. Typically GUIs are provided vianetwork-based Java clients (such as Client 1 913.1 and Client 2 913.2)executing on PCs, Workstations, or other similar computing elements. Theclients include interface functions (such as Interface 915.1 andInterface 915.2) to facilitate processing of GUI commands and display ofGUI data, as well as communication of commands and data. GUIs generallyoperate on managed objects (such as provisioned servers), and typicallyindependently maintain state information about the managed objects (i.e.the GUIs are “stateful”). GUIs update in real time as status of managedobjects changes in real time. Communications between the GUIs and theEnterprise Manager (such as CIM Communication 1 916.1 and CIMCommunication 2 916.2) may be transported via any combination of WAN(including the Internet), MAN, LAN, or a direct connection to anycompatible communication interface provided by ES1 110A, according tovarious embodiments. For example, communications between GUIs and theEnterprise Manager may be coupled via an Ethernet port provided by oneof NMs 130, or by Management I/O 412 (FIG. 4A), according to embodiment.

CLIs enable all or any subset of system management and configurationcontrol operations available via GUIs, according to embodiment. In someembodiments, CLIs enable somewhat limited functionality with respect tothe GUIs. CLIs are typically provided via network-based text-orientedcommand shells (such as Shell 1 910.1 and Shell 2 910.2) executing onPCs, Workstations, or other similar computing elements. The shells andrelated SW include interface functions (such as Interface 912.1 andInterface 912.2) similar in operation to the client interface functions.CLIs are typically stateless, relying on the Platform Manager 531 tomanage objects on their behalves. The CLIs send commands to the PlatformManager for translation into operations on managed objects (such asprovisioned servers). Communications between the CLIs and the PlatformManager (such as CORBA Communication 1 916.3 and CORBA Communication 2916.4) may be transported via any of the mechanisms provided for thecommunications between the clients and the Enterprise Manager. In someembodiments, CLIs, low-level services supporting CLIs, or both, areprovided by SW executing on resources of ES1 110A, such as CLI 532 (FIG.5B) executing on Primary SCM 140A.

One or more GUI sessions may be simultaneously active and incommunication with the Enterprise Manager, receiving data and providingcommands in real time. The Enterprise Manager updates Secondary CIMInstance Repository 917.S according to the commands received from all ofthe GUI sessions. Similarly, one or more CLI sessions may besimultaneously active and in communication with the Platform Manager,receiving data and providing commands in real time. The Platform Managerupdates Primary CIM Instance Repository 917.P according to the commandsreceived from all of the CLI sessions. Any number of GUI sessions andany number CLI sessions may also be active concurrently, and theEnterprise and Platform Managers receive and process the respectivecommands, synchronizing the two repositories as necessary.

In some embodiments, GUIs and CLIs provide an integrated view ofprocessing and networking functions available in an ES system. In otherembodiments, GUIs and CLIs provide a “legacy” view of logically separateelements including switches, routers, accelerators for Layer-4 toLayer-7 processing (such as SSL accelerators), management servers, andenterprise servers. In still other embodiments, GUIs and CLIs providingintegrated and legacy views may be operated simultaneously.

Platform Manager 531 (and closely cooperating SW modules) functionsperformed include HW and SW inventory discovery and maintenance, SWservices relating to internal subsystem management and RAS, networkingservices, low-level user interface services, and component levelservices. A single Application Programming Interface (API) is providedby Platform Manager 531 to enable accessing the aforementioned functionsby other SW modules (such as Enterprise Manager 530, and CLI 532, forexample).

HW and SW inventory discovery functions include any combination ofseveral elements, according to various embodiments. A chassis manager(such as CM 533 of FIG. 5B) discovers and manages chassis resources, aquery engine (such as Query Engine 534) processes queries, and apersistent state manager (such as Repository Manager 535) records andprovides system configuration, status, and query information. A VIOCmanager (such as VIOC Manager 536) provides control information directlyto VIOCs via the SFM, and indirectly interfaces to VIOC Drivers via thescratchpad registers included in the VIOC. A write to any of thescratchpad registers typically results in an interrupt being deliveredto a VIOC Driver. An interface manager (such as Interface Manager 537)discovers interfaces on NMs and detects changes in state on NMs. In someembodiments, a VLAN Manager (such as VLAN Manager 539) provides servicesand operations relating to VLANs, such as some aspects of provisioningVLANs in relation to VIOCs. An event service includes a general publishand subscribe message layer and an alarm service enables managementprocesses to set and clear alarms. A software versioning and upgradeservice enables management of binary software releases.

Internal subsystem management SW services include, according to variousembodiments, an Interface Definition Language (IDL) based communicationinfrastructure for use between various system components. The IDL-basedinfrastructure is also used for process management and monitoring (viaSNMP, for example) of system components, services, and applications, andalso for use for information logging from one or more processors.

Other internal subsystem management SW services are provided, accordingto embodiment. Security services and virtualization services (relatingto modularity and ownership records of system components and resources,for example) may be provided. Maintenance services (relating to apersistent database to store configuration and other related informationacross system restarts and failures, for example) may be provided. Anaming service (serving name and location information to processesexecuting on resources inside a chassis, and to executing agentsexternal to the chassis, for example) may be provided. An IPCcommunication framework and associated services (for communicationbetween management and controlplane processes) may be provided. Alow-level CLI (for accessing various platform manager functions) may beprovided.

RAS SW services include, according to various embodiments, statereplication, quorum protocols, fast restart mechanisms, productvalidation techniques, support for in-service upgrades, and statisticsand tracing collection and storage. Platform manager functions furtherinclude, according to embodiment, an interface for Enterprise Manager530, a debugging infrastructure, a highly available processinfrastructure (with disaster recovery), and various support functionsrelating to security, logging in, filtering and secure communication.

Networking services include, according to various embodiments, L2 and L3protocols and functions, such as those associated with management of FIBdata, and Routing Information Base (RIB) data, respectively. Accordingto embodiment, networking services further include selected Layer 4 andabove services, and protocols and services relating to SNMP ManagementInformation Base (MIB) data and SNMP agent support for externalmanagement systems.

Component level services include, according to various embodiments,services and frameworks relating to management of processing resourcesincluded on NMs, FCMs, OLBs (including system and user code), and PMMs.An example of such a framework is a configuration framework to be usedby CLIs, SNMP agents, the Enterprise Manager (via a GUI), and othersimilar mechanisms to deliver configuration information to components.An example of such a service is a boot management service to providesupport and boot image management for booting pluggable modules (such asPMMs, NMs, FCMs, and OLBs) in a system.

Enterprise Manager 530 functions performed include multi-chassisfunctions analogous to functions performed by the Platform Manager,selected complex provisioning operations, and interfacing to GUIs(described elsewhere herein). In some embodiments, the EnterpriseManager includes functions to integrate one or more ES systems intosurrounding management infrastructure.

SCF and Related Tasks

FIG. 10 illustrates a conceptual view of an embodiment of a ServerConfiguration File (SCF) and related SCF tasks. SCF Tasks 1010 operateon SCF 1020 as illustrated by Interaction 1030 between SCF Tasks 1010and SCF 1020. SCF 1020 serves to describe a desired server by specifyinga list of required (or desired) resources, typically in the form ofconstraints. A server specification, as illustrated by SCF 1020, mayinclude HardWare (HW) details such as HW Specifications 1021, and SWdetails such as OS Specifications 1022. Additionally, various HW and SWattributes and organization and operational details may also be includedin SCF 1020, as illustrated by Server Attributes 1023.

According to various embodiments, SCF 1020 may be implemented as ahuman-readable text file or as a machine-readable binary file. Typicallytext file implementations enable editing and viewing operations viastandard text editors. Typically binary file implementations enableediting and viewing operations via a specialized Command Line Interface(CLI) or a specialized GUI. In some embodiments, text file SCFimplementations may provide CLI and GUI driven editing and viewingoperations.

Tasks that may be performed on an SCF include creating an SCF, asillustrated by Create 1011, and modifying an SCF (including editing), asillustrated by Modify 1012. An SCF may be explicitly locked to preventinadvertent or unauthorized modifications, and explicitly unlocked toallow modifications, as illustrated by Lock/Unlock 1013. Viewing an SCF,as illustrated by View 1014, enables examining the SCF to inspectvarious details (such as parameters in HW Specifications 1021, OSSpecifications 1022, and Server Attributes 1023). In some embodiments,View 1014 may provide error checking operations to determine if the SCFis legal and is syntactically correct. An SCF may be copied, asillustrated by Copy 1015, moved (or renamed) as illustrated by Move1016, and removed, as illustrated by Remove 1017.

HW Specifications 1021 may describe constraints in a logical manner (forexample ‘CreateServer 2way SMP’) or in a physical manner (for example‘CreateServer 2way SMP-slot 2’, referring specifically to HW insertedinto slot 2). The HW specifications may include a combination of logicaland physical specifications. In some embodiments, the constraints areinterpreted by default as minimum (i.e. ‘CreateServer 2way SMP’ may besatisfied by one or more 2-way SMPs), and may be specified explicitly tomatch exactly (for example ‘CreateServer 2way SMP-exact’ only allows fora single 2-way SMP). Constraints for some types of resources (such asVNICs, for example), may be described by a full or a partialspecification. The full specification is expressed by itemizing andfully specifying each individual resource (enumerating bandwidth,priority scheme selection and associated weights, and other similarparameters, for example). Alternatively, the partial specification isexpressed by listing a number of a particular type of resource required(each of the resources is assumed to require identical parameters, forexample).

Server Operational States

FIG. 11 illustrates selected aspects of an embodiment of serveroperational states and associated transitions. Flow typically begins at“Unused” 1101 with a defined SCF (such as SCF 1020 of FIG. 10, forexample) and an available resource collection (such as HardwareResources View 900A of FIG. 9A). When a command to pin a server isreceived, flow proceeds along “PinServer” 1111 to “Pinned” 1102, whereresources are assigned (or allocated) from the available resourcecollection according to constraints in the SCF. In some embodiments,resource allocation (or binding) is managed by a platform manager (suchas Platform Manager 531 of FIG. 5B). The result of the pinning is aprovisioned server (such as any of Provisioned Server PS₂ 902.2,Provisioned Server PS₁ 902.1, and Provisioned Server PS₀ 902.0illustrated in FIG. 9B).

In various embodiments, there may be further processing relating topinning a server, such as programming resources based in part on theassignment, based in part on attributes specified in the SCF, or anycombination thereof. For example, the SCF may specify a two-processorconstraint, and during processing relating to “Pinned” 1102 anassignment of SMP Portion P_(A) 152A is made from an available resourcepool originally including SMP Portion P_(A) 152A and SMP Portion P_(A′)152A′ (see FIGS. 9A and 9B, for example). SMP 151A (see FIG. 1B, forexample) may then be configured as the pair of two-processor physicalpartitions 152A and 152A′ (if this has not already been accomplished).

VNIC 154A.1 may also be configured with an IP address, a MAC address, aVLANid, and so forth, according to information in the SCF or accordingto other management related criteria. Selected lookup state information(such as keys and results illustrated in FIG. 8A and FIG. 8B) may beprogrammed, including a VNIC MAC destination address (MACDA) tocorresponding fabric port mapping, for subsequent reference by VIOCswhen processing packets (and messages). Other programming may beperformed relating to VLAN membership, bandwidth, queuing behaviors, orother related properties (such as programming any combination of VNICregisters including those of Address Block 601.1 and VNIC ConfigurationBlock 618.1 of FIG. 6A).

When a command to install the server is received, flow proceeds along“InstallServer” 1112 to “Installing” 1103 where initial operatingsoftware is installed. The initial operating software includes anycombination of a boot image, an OS boot loader, a root file systemimage, portions of an OS image, and an entire OS image. The software iscustomized as required according to attributes included in the SCF, andstored so that it is accessible by hardware resources assigned duringprocessing relating to “Pinned” 1102. If installation fails, then flowproceeds along “Failure” 1113.F to “Failed” 1109, where correctiveaction may be taken. If installation is successful, then flow proceedsalong “Success” 1113 to “Installed” 1104.

When a command to boot the server is received, flow proceeds along“BootServer” 1114 to “Booting” 1105, where execution of the boot imagebegins, followed by execution of the OS boot loader, with references tothe root file system image as needed. If booting fails, then flowproceeds along “Failure” 1115.F to “Failed” 1109, where correctiveaction may be taken. If booting is successful, then flow proceeds along“Success” 1115 to “Running” 1106. The server is then fully operationalwith an executing OS, and may begin executing various applicationprocesses. In situations where installation has been performedpreviously, the server may be booted directly from “Pinned” 1102 via“BootServer” 1112.B.

“Running” 1106 is exited when any of several server operationalcommands, including shutdown, reboot, and reclaim are received, asillustrated by “ShutdownServer, RebootServer, ReclaimServer” 1116. Inthe case of a shutdown command, flow proceeds to “Shutting Down” 1107,where any executing applications are closed and the executing OS isterminated. When termination is complete, then flow proceeds along“ShutdownServer” 1117 to “Pinned” 1102, awaiting the next command In thecase of a reboot command, flow proceeds to “Shutting Down” 1107 (wheresoftware execution is terminated) and then proceeds along “RebootServer”1117.B to “Booting” 1105 to boot the server again.

In the case of a reclaim server command, flow proceeds to “ShuttingDown” 1107 (terminating software) and then proceeds along“ReclaimServer” 1117.R to “Unused” 1101, where processing frees theresources assigned when pinning the server and returns them to theavailable resource collection. A reclaim server command may also beprocessed from “Installed” 1104 (via “ReclaimServer” 1114.R) and from“Pinned” 1102 (via “ReclaimServer” 1112.R). When an SCF is unused (as in“Unused” 1101, after processing of a reclaim server command, forexample), the unused SCF may be deleted, as indicated by flow“DeleteServer” 1111.D proceeding to “Deleted” 1108.

The initial operating software, in various embodiments, may correspondto a generic operating system environment (such as Linux, Windows, orany similar commercially available OS). In other embodiments, theinitial operating software may correspond to a wholly or partiallycustomized operating system environment, according to user requirements.Such customization may be based in part on one of the commerciallyavailable generic operating system environments. As illustrated in FIG.5A, in some embodiments the initial operating software may include aHypervisor (such as Hypervisor1 510 or Hypervisor2 520).

In some embodiments, operations such as those illustrated in SCF Tasks1010 may be performed on an SCF only while there is no correspondingprovisioned server, as designated by “Unused” 1101. The previousdiscussion of SCF Tasks assumes this scenario, and is roughly analogousto operating on the SCF when a server is “off-line”. However, otherembodiments enable some or all SCF Tasks to be performed while a serveris “on-line” (i.e. in any combination of operational states “Pinned”1102, “Installing” 1103, “Installed” 1104, “Booting” 1105, “Running”1106, and “Failed” 1109, in addition to “Unused” 1101). For example,Modify 1012 may be performed while a server is running, in order to addresources associated with the server, and has the effect of changing theSCF as well as pinning additional resources that are then made availableto the running server. Similarly, resources may be subtracted from therunning server via Modify 1012. Parameters that may be modified while aserver is running are considered dynamic parameters, and parameters thatmay not be modified are considered static parameters. Various parametersmay be dynamic or static, according to implementation.

The operation of various SCF Tasks with respect to server operationalstate (such as Running and Unused) may also vary by embodiment. Forexample, in some embodiments, when View 1014 is performed, informationspecific to the operational state of the server corresponding to theselected SCF may be provided. This information may include currentoperating state, any relevant error information, data concerningprocessing load, and other similar information relating to status of anon-line server. In alternate embodiments, variants of the View operationmay provide a system-wide listing of defined SCFs and any correspondingserver operational state.

A server as defined by an SCF may be physically relocated from one setof resources to another, including resources in distinct geographicallocations, according to various embodiments. In a first embodiment, anSCF may be developed on a first EF system and then the SCF may be usedon a second EF system. This effectively deassigns resources for theserver from the first EF system and then assigns resources for theserver from the second EF system. The two systems may be co-located in asingle server facility, or located in geographically distinct serverfacilities. In a second embodiment, a server provisioned according to anSCF may be unpinned with respect to a first assignment of resources, andthen pinned anew to a second assignment of resources.

Real Time Server Provisioning and Management

Real time server provisioning and management includes recognizing systemstatus changes and responding to the system status changes atapproximately the same rates, and performing these operations with lowlatency. As an example, when a pluggable module is inserted into arunning ES, availability of new HW resources included in the pluggablemodule is reflected immediately to an operator of the ES, according to apreviously recorded query. The operator may then request booting a newprovisioned server, and this request is performed immediately (providedsufficient resources are available to provision the server).

At the level of a single chassis, CM 533, executing on an SCM (such asPrimary SCM 140A), manages many aspects of real time server provisioningand management, including managing modules in the chassis andmaintaining an inventory of modules in the chassis. The CM also monitorsoperational status of the modules and provides user interfaces forconfiguration of modules and provisioning of servers (via CLIs or GUIs,as provided directly by the CM or in conjunction with other SW,according to various embodiments). Additional information concerning theCM is included elsewhere in this section (see also the Chassis ManagerOperation section, elsewhere herein). Operating in parallel with the CM,instances of Module BMC SW 550, executing on BMCs in the system (such asBMCs 402.4, 402.5, and so forth), provide events to and receive commandsfrom the CM. The events convey information regarding module statuschanges and command execution results, providing information necessaryfor module management and inventory maintenance.

FIG. 12A is a flow diagram illustrating selected operational aspects ofreal time server provisioning and management in an ES system embodiment,including “CM SW Flow” 1201.20 and “Module BMC SW Flow” 1201.21. The CMflow illustrates portions of processing performed directly by or underthe control of CM 533 (FIG. 5B). The BMC flow illustrates portions ofprocessing performed directly or under the control of the Module BMC SW550 (FIG. 5C) executing on the BMCs.

Processing begins when a module (a PMM, such as PMM 150A, for example)is introduced into an ES chassis backplane (“Module Insertion” 1201.1),and continues as a presence interrupt is generated and delivered to CM533, indicating insertion of the pluggable module (“Detect ModuleInsertion and Generate Presence Interrupt” 1201.2). Processing thencontinues under the control of the CM, as illustrated in “CM SW Flow”1201.20.

When the CM receives the presence interrupt, a request is made toestablish communication between the CM and a BMC included on theinserted module, such as BMC 402.5 of PMM 150A (“Establish TCP IP withModule BMC” 1201.3). In parallel, the module BMC has been powered (dueto insertion of the module) and has begun booting. Depending on variousimplementation dependent timing behaviors, the module BMC may havecompleted booting. Eventually the BMC completes booting, responds to theTCP/IP communication channel, and listens for commands from the CM (byexecuting various portions of Command Agent 553 of FIG. 5B, forexample).

At this point, CM 533 is aware only that a module has been inserted, butis not aware of any particular details of the module (such as if themodule is a PMM, NM, FCM, or OLB). The CM then interrogates the modulefor Vital Product Data (VPD) to determine the particular details of themodule (“Request VPD” 1201.4) by issuing a Module Get VPD command to themodule BMC. The CM then awaits a BMC event in response to the command(“Event Available?” 1201.5), looping back (“No” 1201.5N) until aresponse is received (“Yes” 1201.5Y).

In parallel, the BMC SW receives the command (as illustratedconceptually by dashed-arrow 1201.4V) and begins to gather the VPD forthe module. Depending on embodiment, optional power-up processing mayoccur (“Optional Power-Up” 1201.10 via dashed-arrow 1201.4P) to enablevarious components on the module to respond to BMC interrogatoriesconcerning various capacities and capabilities. For example, in someembodiments it may be necessary for a portion of the module to operatein a reduced or full manner in order to determine a maximum operationalfrequency, which may be an element of the VPD. The various elements ofthe VPD are eventually gathered from components of the module (“GatherVPD” 1201.11). The BMC SW flow then proceeds to send an event (“Send VPDEvent” 1201.12) to the CM in response to the command (as illustratedconceptually by dashed-arrow 1201.12V). Processing relating to sendingthe event is generally performed by executing various portions of EventAgent 552 (5B), for example.

In parallel, the CM has been awaiting a response from the BMC, and whenan event arrives conveying the response, the VPD included in theresponse is parsed and corresponding entries are stored into arepository (“Post Event Data to Repository” 1201.6 via “Yes” 1201.5Y).In some embodiments, the repository is Primary CIM Instance Repository917.P (FIG. 9C) and Repository Manager 535 accesses the repository atthe request of CM 533. In some embodiments, the repository includes anycombination of Primary CIM Instance Repository 917.P and Secondary CIMInstance Repository 917.S.

The CM then processes queries that depend on at least one of thecorresponding entries stored in the repository (“Pre-Select Queries andRespond to Activated Queries” 1201.7). Processing includes determiningqueries that are dependent on any of the newly stored entries (or“pre-selecting” such queries), evaluating the pre-selected queries (todetermine which, if any, are activated or deactivated), and processingany resultant triggered queries (and ceasing processing of any queriesthat are no longer triggered). In some embodiments, query processing isperformed via SW routines included in Query Engine 534 (FIG. 5B). Flowthen loops back to await a subsequent event (“Event Available?” 1201.5).

In parallel to the processing of the VPD data by the CM, the BMC SW hasentered a loop monitoring for status changes on the module (“StatusChange?” 1201.13). If no change has occurred, then processing loops back(“No” 1201.13N). If a change has occurred, then processing flows forward(“Yes” 1201.13Y) to send a status change event indicating and describingthe new status to the CM (“Send StatusChange Event” 1201.14). The eventcommunication is indicated conceptually by dashed-arrow 1201.14E,pointing to “Event Available?” 1201.5, where the CM is looping whileawaiting a newly available event.

In some embodiments, processing of triggered queries may result in oneor more commands being sent to the BMC to alter the status orconfiguration of the module (as illustrated conceptually by dashed-arrow1201.7C, for example). For example, a query may be registered that isactivated whenever a module is inserted, and the query may result in anaction including provisioning a server. If the module is a PMM, thenprovisioning the server may require sending a command to the BMC on thePMM module to partition the PMM according to the requirements of theserver to be provisioned. Other such scenarios are possible, such asre-provisioning a failed server when a replacement module is inserted.

Generally the BMC SW is enabled to receive and process commands inparallel with performing other processing. The received BMC commands aretypically generated by the CM, and in some embodiments are provided inresponse to server provisioning and management commands, that may beprovided manually by a user, or generated automatically in response toan activated query, according to various usage scenarios. Examplesinclude booting a server, such as processing related to “BootServer”1114 (FIG. 12), and shutting down a server, such as processing relatingto “ShutdownServer” 1117.

Typically a command is sent asynchronously to the BMC (“Command”1201.15), as a result, for example, of processing related to anactivated query (see dashed-arrow 1201.7C originating from “Pre-SelectQueries and Respond to Activated Queries” 1201.7. The command is thenreceived, any accompanying parameters are parsed, and the requiredoperation is performed (“Perform Command” 1201.16). Status that maychange as a result of executing the command is updated (“Update Status”1201.17) and processing of the command is complete (“End” 1201.18).Updating the status, as shown conceptually by dashed-arrow 1201.17S,eventually results in recognition of the status change (“Yes” 1201.13Yexiting “Status Change?” 1201.13). In turn, an event is sent to the CM(dashed-arrow 1201.14E), typically including a response to the command

Recognized status changes (“Status Change?” 1201.13) are not limited tothose occurring as a result of processing a command, but may include achange in any monitored parameter, state, or other related variableassociated with the module. Such status changes may include a modulefailing or becoming operational or powered up, a sensor crossing athreshold, or completion of a boot operation. See the Selected BMC EventDetails section, included elsewhere herein, for other examples.

Those of ordinary skill in the art will recognize that the figure isillustrative only, as only selected portions of the CM and BMC SW flowsare shown. Furthermore, the CM is typically in communication with aninstance of BMC SW associated with each inserted module of an ES systemembodiment. Thus there are typically multiple instances (operating inparallel) of the illustrated flow.

Those of ordinary skill in the art will also recognize that although thefigure illustrates loop back control (such as “Event Available?” 1201.5)implemented as a “busy loop”, in alternate embodiments an interrupt maybe used instead. These and all similar variations are contemplatedaccording to various embodiments.

FIG. 12B is a flow diagram illustrating selected operational aspects ofreal time server provisioning and management in an ES system embodiment,including selected details relating to provisioning VNICs and bootingPMMs, as typically performed during processing related to “Booting” 1105(see FIG. 11). FIG. 12B is representative of operations performed byvarious SW elements, including the CM, the BMC SW, the VIOC Manager, andthe BIOS, OS, and VIOC drivers executing on a PMM.

Flow starts (“Begin” 1202.1) when a command or request to boot a serveris processed. In response the CM instructs the BMC to partition the PMMaccording to an SCF, and the BMC configures the HT links on the PMM toform the appropriate physical partitions (“Partition PMM” 1202.2). Insome embodiments the BMC also “constructs” or “routes” a VIOCimplementation in all or a portion of a Field Programmable Gate Array(FPGA) device (“Instantiate VIOC from FPGA” 1202.3). In some usagescenarios a plurality of VIOCs may be instantiated, such as VIOC 301.5and VIOC 301.5′ of PMM 150A (FIG. 4B). In other usage scenarios afurther plurality of VIOCs, included on a plurality of PMMs, may beinstantiated, depending on the requirements stated in the SCF.

After the VIOC (or VIOCs) are instantiated, the CM provides VNICprovisioning information from the SCF to a controlplane process (such asVIOC Manager 536 of FIG. 5B) responsible for configuring VNICs in theVIOC (“VNIC Provisioning Info to VIOCmgr” 1202.4). The VNICs are thenconfigured according to the provisioning information (“Configure VNICs”1202.5), typically by asserting corresponding VNIC enable bits (such asVNIC Enable 618.1 a of FIG. 6A) of respective VNICs. In someembodiments, the VNIC configuration further includes setting minimum andmaximum bandwidth parameters (such as Bandwidth Minimum 618.1 d andBandwidth Maximum 618.1, both of FIG. 6A), as specified in the SCF.Subsequently, lookup information is programmed into TCAM/SRAMs coupledto the VIOC (“Configure TCAMs” 1202.6), based in part on the SCF andalso based on additional system configuration and topologicalinformation.

The PMM configuration (including partitioning and VIOC setup) is nowcomplete and processing continues by booting the PMM (or PMMs) used inthe instantiated server (“Boot PMMs” 1202.7). Processing in the PMMcontinues as an OS (such as OS1/Drivers 1 507 of FIG. 5A) is booted(“Start OS” 1202.8). A kernel mode VIOC Driver (such as VIOC Driver 1511) is in turn initialized and spawned by the OS (“Start VIOC Driver”1202.9). The VIOC Driver is typically responsible for communicationbetween the OS and selected VIOC resources, including VNICs. The VIOCDriver subsequently instantiates OS-level interfaces for each of theconfigured VNICs, presenting the VNICs as NIC resources to the OS(“Present NICs to OS” 1202.10). Presenting the NICs includes the VIOCDriver reading the VNIC enable bits implemented in the VIOC, and foreach asserted bit (indicating an active VNIC), allocating andinitializing driver-level SW data structures for the respective enabledVNIC to enable the OS to access the VNIC as a NIC. The illustratedprocessing is then complete (“End” 1202.9).

Removal of a VNIC (as a result of operations relating to servermanagement, for example) is typically accomplished in several stages.The VIOC Manager disables a corresponding VNIC enable bit in (includedin a VNIC enable register of a VIOC). In response to writing the VNICenable register, the VIOC generates an interrupt that is delivered tothe VIOC Driver executing on the module including the VIOC (such as aPMM). The VIOC Driver reads the VNIC enable register, determines that aVNIC has been disables, and deletes any corresponding OS-levelinterfaces previously configured and presented to the OS.Reconfiguration of a VNIC, with respect to properties visible to the OS,is accomplished in a similar manner: the VIOC Manager writes VIOCregisters, an interrupt is delivered to the VIOC Driver, and the VIOCDriver modifies corresponding OS-level interfaces appropriately. Resultsmay be returned by the VIOC Driver by writing one or more VIOCscratchpad registers with return value information. Typically the VIOCManager polls the proper scratchpad registers awaiting results.

In some embodiments, the VIOC Manager executes using resources on an SCM(such as Primary SCM 140A), and in such embodiments the VIOC Drivertypically communicates via an SFM with the Manager (as shown by PMM-SCMData Exchange 215, for example). In some embodiments, one or more of theVIOC Drivers communicate with the same VIOC Manager, and or more of theVIOC Drivers communicate with the same VLAN Manager. In someembodiments, there is only a single VIOC Manager and a single VLANManager.

BMC Command and Low-Level Hardware Boot Processing

FIG. 13A is a state diagram illustrating processing of selected BMCrelated commands in an ES embodiment. In some embodiments, all or anyportion of BMC commands are implemented as IPMI type commands, and insome of these embodiments, an IPMI Client (such as PMI Client 551 ofFIG. 5C) may provide interface functions for communication with CommandAgent 553. The BMC commands are typically provided by CM 533 andprocessed by BMC SW, as illustrated by “Perform Command” 1201.16 (FIG.12A).

In some embodiments, the BMC SW implements processing of BMC commandsvia a BMC Operational State Machine, and the figure is representative ofstates and transitions of these embodiments. In other embodiments, theBMC command processing is performed by any combination of SW and HW. Insome embodiments, a plurality of BMC state machine instances areprovided on a module (such as a PMM), one for each possible partitionthe module may be partitioned into. In some embodiments, the BMCOperational State Machine receives IPMI commands and passes them throughto an IPMI implementation, returning IPMI status from the IPMIimplementation if needed. Some BMC events correspond to pass-throughIPMI events, such as Sensor Threshold Breached, described elsewhereherein. The figure conforms to the convention that the state machineremains in a state unless one of the illustrated transitions isactivated (“loopback” transitions are omitted for clarity).

In some embodiments, whenever the state machine transitions to a newstate, the transition is reported to Chassis Manager 533 as one or moreevents that describe the resultant state. The transitions are typicallyrecognized as a status change, such as those detected by “StatusChange?” 1201.13 (FIG. 12A), and event signaling is as illustrated by“Send StatusChange Event” 1201.14. In some embodiments, the eventsinclude information concerning the transition or the cause for thetransition.

Consider the BMC Operational State Machine as starting in state P 1301.In this state, the module the BMC is included in is powered up onlysufficiently for operation of the BMC sub-system, and other elements ofthe module remain powered down. BMC sub-system elements related todetecting selected module status information, receiving CM commands, anddelivering event information to the CM are operational. In someembodiments, these elements include execution of all or portions EventAgent 552, and Command Agent 553 of FIG. 5C.

While in state P 1301, if the CM sends commands including any of ModulePower Up, Module Hold Reset, and Module Boot to the BMC, then the statemachine transitions to state C1 1302 via transition “Power Up OR HoldReset OR Boot” 1301.C1. State C1 generally corresponds to a first orminimal configuration. If the command was Module Power Up, then state C11302 is the end state for processing the command If the command wasModule Hold Reset, then when conditions for transition “Valid BCT ANDConfiguration Complete OK” 1302.C2 are met, the state machinetransitions to state C2 1303, and this is the end state for processingthe Module Hold Reset command State C2 generally corresponds to a secondor customized configuration. If the command was Module Boot, then thestate machine transitions first to state C2 1303 as Module Hold Reset.Then, when conditions for transition “Boot” 1303.S1 are met, the statemachine transitions to state S1/D 1304, followed by a transition tostate S2 1305 when conditions for transition “Heartbeat OK” 1304.S2 aremet, and this is the end state for processing the Module Boot command.

While in state C1 1302, power is applied to all of the elements on themodule, in addition to the BMC sub-system, and reset is active to anysystem or application processing elements. For example, CPUs included onPMMs, PCEs and TMs included on NMs, IOPs included on FCMs, and CPUsincluded on OLBs are continuously reset. If a Module Power Up commandwas being processed, then C1 is the final state, and is exited only uponreceipt of another command If a Module Power Down command is received,then the state machine transitions to state P 1301 via transition “PowerDown” 1302.P. If a Module Force Fault command is received, then thestate machine transitions to state F 1306 via transition “Force Fault”1302.F.

If a Module Hold Reset or a Module Boot command is being processed, thenC1 is a transient state, and is exited when the BMC sub-system detectsor determines that the conditions for transition “Valid BCT ANDConfiguration Complete OK” 1302.C2 are met. Specifically, the BootConfiguration Table (BCT) information received with the command beingprocessed has been found to be valid, and any module configurationinformation included in the BCT information has been successfullyapplied to the module. Thus the module configuration is complete and themachine transitions to state C2 1303.

While in state C2 1303, reset remains active to the system andapplication processing elements. If a Module Hold Reset command wasbeing processed, then C2 is the final state, and is exited only uponreceipt of another command If any command that provides new BCTinformation is received, then the state machine transitions to state C11302 via transition “BCT Change” 1303.C1. If a Module Power Down commandis received, then the state machine transitions to state P 1301 viatransition “Power Down” 1303.P. If a Module Force Fault command isreceived, then the state machine transitions to state F 1306 viatransition “Force Fault” 1303.F.

If a Module Boot command is being processed, then C2 is a transientstate, and is exited when the BMC sub-system detects or determines thatthe conditions for transition “Boot” 1303.S1 are met. Specifically, theBMC determines that an implementation dependent delay has transpired,and the state machine transitions to state S1/D 1304.

While in state S1/D 1304, reset is released, allowing the system andapplication processing elements to begin fetching and executing code. Ifa Module Hold Reset command is received, then the state machinetransitions to state C2 1303 via transition “Time Out OR Hold Reset”1304.C2. If a Module Power Down command is received, then the statemachine transitions to state P 1301 via transition “Power Down” 1304.P.If a Module Force Fault command is received, then the state machinetransitions to state F 1306 via transition “Force Fault” 1304.F.

If a Module Boot command is being processed, then S1/D is a transientstate. If the conditions for transition “Heartbeat OK” 1304.S2 are met,then the state machine transitions to state S2 1305 via transition“Heartbeat OK” 1304.S2. Specifically, the BMC sub-system receives aheartbeat indication from the system or application processor after theprocessor has executed sufficient start-up code (such as BIOS boot for aPMM) to communicate the heartbeat indication to the BMC. In someembodiments, BIOS execution communicates heartbeat information to theBMC via VIOC scratchpad registers.

However, if the BMC does not receive a heartbeat indication after apredetermined time interval, then the BMC Operational State Machinetimes out the operation, and transitions to state C2 1303 via transition“Time Out OR Hold Reset” 1304.C2. A special sub-case of the Module Bootcommand may specify (via information in the BCT) that off-linediagnostics are to be performed instead of a full boot. In this context,completion of the Module Boot command occurs when the off-linediagnostics are completed or have timed out. When this occurs, the statemachine transitions to state C1 1302 via transition “Offline DiagnosticsFinished” 1304.C1.

While in state S2 (the terminus of successful processing of a ModuleBoot command), reset to the processing elements remains released, andthe processing elements continue executing instructions and periodicallygenerating heartbeat indications to the state machine. If apredetermined period of time elapses without a heartbeat indication,then the state machine transitions to state F 1306 via transition“Heartbeat Timeout OR Force Fault” 1305.F.

If a Module Boot or a Module Hold Reset command is received, then thestate machine transitions to state C2 1303 via transition “Boot OR HoldReset” 1305.C2. If a Module Power Down command is received, then atransition is made to state P 1301 via transition “Power Down” 1305.P.If a Module Force Fault command is received, then a transition is madeto state F 1306 via transition “Heartbeat Timeout OR Force Fault”1305.F.

State F is a transient fault recovery state where an attempt is made torecover from whatever condition led to the transition into the state. Ifrecovery from any non-fatal faults relating to state S2 is made, thenthe machine transitions to state F 1306 via transition “Recover”1306.S2. If recovery from any fatal faults relating to states C2, S1/D,or S2 is made, then the machine transitions to state C2 1303 viatransition “Recover” 1306.C2. If recovery from any fatal faults relatingto state C1 is made, then a transition is made to state C1 1302 viatransition “Recover OR Hold Reset” 1306.C1. A Module Hold Reset commandoverrides any in-progress or attempted recovery, and in response themachine transitions to state C1 1302 via transition “Recover OR HoldReset” 1306.C1. A Module Power Down command is similarly overriding, andthe machine moves to state P 1301 via transition “Power Down” 1306.P.The CM may issue a Module Power Down command in response to eventinformation sent from the BMC indicating that the fault is anunrecoverable HW or SW failure, according to embodiment, or represents acatastrophic fault, also according to embodiment.

In some embodiments, some server provisioning and management operationstypically require issuing one or more BMC commands that are processedaccording to the illustrated state diagram. A first example is booting aserver, such as processing related to “BootServer” 1114 (FIG. 12). Ifthe server to be booted is configured with multiple modules (such as twoPMMs), then two separate BMC command streams will be issued, one to eachof the two PMMs (see FIG. 13B for an example). A second example isshutting down a server, such as processing relating to “ShutdownServer”1117, resulting in separate Module Power Down commands to some or all ofthe modules the server was provisioned from.

While the BMC Operational State Machine has been described with respectto selected BMC commands (such as Module Power Up, Module Power Down,Module Hold Reset, Module Boot, and Module Force Fault), this is only arepresentative embodiment. Any combination of BMC commands (such asthose described in the Selected BMC Command Details section, elsewhereherein) may be implemented by the BMC state machine. Additionally, insome embodiments, any combination of BMC Commands illustrated withrespect to the BMC state machine may be implemented by other mechanisms.

Those of ordinary skill in the art will note that the BMC OperationalState Machine may be implemented in HW, SW, or any combination of thetwo, according to embodiment. It is also apparent than any number ofstate machine states and transitions may be implemented to providesimilar functionality, according to embodiment.

FIG. 13B illustrates selected operational aspects of single and dual PMMlow-level hardware boot processing in an ES embodiment, as representedby “Boot PMMs” 1202.7 (FIG. 12B), for example. The processingillustrated in FIG. 13B conceptualizes selected paths through states asillustrated by FIG. 13A, with corresponding states and transitions namedaccordingly. FIG. 13B illustrates boot processing for a single PMMconfiguration (such as P₃ 203 of FIG. 2) and a dual PMM configuration(such as P₄ 204 of FIG. 2), and as such the generic Module commandsdescribed in FIG. 13A transitions correspond to specific PMM Modulecommands in the context of FIG. 13B.

Operation in the single PMM configuration is as follows. “Boot Flow”1312 begins at state P 1301.M, when the BMC on PMM 150B receives a PMMBoot command via CM 533. The BMC Operational State Machine then moves tostate Cl 1302.M via transition “Boot” 1301.C1.M, and asserts reset tothe PMM. When the BCT has been found to be valid and the configurationincluded therein has been properly applied to the PMM, the state machinemoves to state C2 1303.M via transition “Configuration Complete OK”1302.C2.M. The state machine then continues to state S1/D 1304.M viatransition “Boot” 1303.S1.M, and releases reset to the PMM. The PMM thenboots BIOS and generates a valid heartbeat. When the valid heartbeatfrom the PMM has been detected by the BMC, the machine moves to state S21305.M via transition “Heartbeat OK” 1304.S2.M, and the PMM boot flow iscomplete.

Each of the state machine transitions are reported to CM 533 via eventsdescribing the resultant state. For example, when the state machine hascompleted the transition to state C1 1302, an event describing the newstate machine state as “C1” is generated and delivered to the CM. Eventsare similarly generated and delivered for all of the state machinetransitions.

Operation in the dual PMM configuration is as follows, with PMM 150Boperating as the master, and PMM 150A operating as the slave.Conceptually, the master PMM is partially booted (“Hold Reset Flow”1313M), then the slave PMM is booted (“Hold Reset Flow” 1313S and“Release Reset Flow” 1314S), and then the master PMM is fully booted(“Release Reset Flow” 1314M). The final slave PMM boot state isdifferent than the master PMM boot state, as the slave PMM omits bootingof BIOS and hence generates no heartbeat. Coordination of transitionsbetween the master and slave PMMs are managed by CM 533, via receptionand processing of state transition events and issuing of appropriatecommands to the master and slave BMCs on the respective PMMs.

More specifically, “Hold Reset Flow” 1313M begins at state P 1301.M,when the BMC on the master PMM (PMM 150B) receives a PMM Hold Resetcommand from CM 533. The BMC Operational State Machine then moves tostate C1 1302.M (asserting reset to the master PMM) and then to state C21303.M as in “Boot Flow” 1312. However, the state machine remains instate C2 1303.M when processing the PMM Hold Reset command (leavingreset asserted), instead of continuing as when processing a PMM Bootcommand As in all of the BMC Operational State Machine transitions, anevent is generated upon arrival in state C2 1303.M and delivered to theCM.

In response (indicated conceptually by dashed-arrow 1310) the CM sends aPMM Hold Reset command to the BMC on the slave PMM (PMM 150A). The slaveBMC Operational State Machine then transitions from state P 1301.S tostate C1 1302.S (asserting reset to the slave PMM) and then to state C21303.S, where it remains, awaiting further CM commands An event isgenerated and delivered to the CM indicating the slave BMC is now in the“C2” state. In response the CM provides a PMM Release Reset command tothe slave BMC. The slave BMC then releases reset to the slave PMM andtransitions to state S1/D 1304.S, whereupon another event is deliveredto the CM indicating arrival in the “S1/D” state.

In response (indicated conceptually by dashed-arrow 1311) the CM sends aRelease Reset command to the master BMC. The master BMC then transitionsto state S1/D 1304.M and releases reset to the master PMM. When BIOSboot is complete and the resultant heartbeat is detected, the master BMCOperational State Machine transitions to state S2 1305.M and reports thenew state to the CM. Booting of the dual PMM configuration is nowcomplete, with both PMMs out of reset and the master PMM having bootedBIOS.

According to embodiment, CM communication with BMCs is via anycombination of transports and protocols. The transports include Ethernet(coupling 452 of FIG. 4A, for example, as described elsewhere herein),an Intelligent Chassis Management Bus (ICMB), an Intelligent PlatformManagement Bus (IPMB), RS-485, RS-232, PCI mailboxes, in-band orout-of-band signaling over the SFM, and any other similar mechanisms.The protocols include TCP/IP and any similar protocols. Thecommunications include events from BMCs to the CM, and commands from theCM to the BMCs.

Some embodiments provide for larger than 8-way SMPs, and in a firstgroup of implementations, BMC coordination is via explicit CM control,as illustrated in FIG. 13B. In a second group of implementations, BMC SWinstances communicate and cooperate with each other in a peer-to-peermode, independent of explicit CM control coordination and sequencing.

Selected BMC Event Details

BMC events are generated when a change in specific characteristics of anES system or a pluggable module included therein occurs, and are alsogenerated in response to most BMC commands (even those effecting nochange in characteristics). The CM is the primary consumer of thegenerated events. At boot up of each pluggable module (such as a SIM,PMM, NM, FCM, and OLB), the CM establishes a separate TCP connection foreach respective BMC, for communication of the events as TCP messages.Each of the TCP messages may include a returned data structure providingspecific details regarding the event, such as detailed status or loginformation, according to embodiment. The data structure typicallyincludes fields identifying the pluggable module type sourcing theevent, and the event classification or number. SIMs, PMMs, NMs, andOLBs, may be identified as pluggable module types 1, 2, 3, and 4,respectively, with unknown modules identified as module type 0,according to embodiment. In some embodiments, a dedicated packet formatis used to convey event information. In some embodiments, BMC events areconveyed as SNMP traps.

Pluggable modules including VIOCs (for example SIMs, PMMs, FCMs, andOLBs) communicate events specific to VIOC operation, such as VIOCInitialization Complete/Fail, and VIOC Reset Request. The VIOCInitialization Complete event is sent when the BMC has successfullyinitialized the VIOC after module reset has been released, and the VIOCInitialization Fail event is sent if the VIOC initialization fails. Insome embodiments, the VIOC Initialization Complete and Fail events areimplemented as a single event with a field in the associated return datastructure specifying success or failure. The VIOC Reset Request event issent by the BMC in response to receipt of a corresponding VIOC resetrequest from a VIOC Driver executing on the module. The CM determines ifand when permission for the request is to be given, and if so sends acorresponding Module Reset VIOC command to the BMC, providing amechanism for the VIOC Driver to reset an associated VIOC under controlof the CM.

Other BMC events include Module Operational Status Up/Down, ReleaseReset Failure, and Sensor Threshold Breached. The Module OperationalStatus Up/Down event is sent when the BMC successfully establishes aheartbeat with SW executing on the module. The associated return datastructure specifies that the module is operational (Up). Subsequently,if the heartbeat is not received within a predetermined time interval,then the BMC sends the event with the data structure indicating themodule is not operational (Down). In some embodiments, separate eventsare used for Module Operational Status Up and Module Operational StatusDown. The SW executing on the module and providing the heartbeat may beany combination of OS SW, Driver SW, and BIOS SW, varying according tomodule type and embodiment.

In some embodiments, the Module Operational Status Up/Down event is sentwhen the BMC Operational State Machine transitions to state S2 1305(FIG. 13A), with the return data structure indicating the module isoperational. In some embodiments, a general BMC State Change event maybe used to communicate transitions of the BMC Operational State Machine,including transitions such as the transition to state S2 1305., as wellas other transitions of the state machine.

The Release Reset Failure event is sent when the BMC detects that amodule fails to respond to a request to release reset, typicallydelivered to the module by the BMC in response to a correspondingcommand from the CM. The Sensor Threshold Breached event is sent whenany sensors included in the BMC sub-system report a value that crossesany predefined thresholds (for example an over-temperature orover-voltage detection). The event data structure may optionally includethe sensor value at the time the event is detected, according to sensortype and embodiment.

PMM specific events generally relate to a BCT, that is typically asuperset of a Partition Configuration Table (PCT), used to specify theconfiguration of a PMM, particularly with respect to the number of CPUsin a partition (such as 2-way, 4-way, or 8-way). PMM specific eventsinclude a BCT Valid event that is sent in response to a BMC command thatcommunicates a BCT. The BMC checks the communicated BCT to determinethat it is valid for the module (such as determining that a requestedpartitioning is possible for the module), and if so, then configures themodule according to the information in the BCT. If the configuration issuccessful, then the BCT sends a BCT Valid event indicating that the BCTwas valid for the module, and the module was successfully configured asspecified by the BCT.

SIM specific events include Power Up/Down and Fan Up/Down events. ThePower Up/Down event is sent when there is a change in the operationalstatus of a power module in the system. The event data structurespecifies if the module has become operational (Up) or has becomenon-operational (Down). Similarly, the Fan Up/Down event is sent tonotify the CM of a change in a fan module operational state. In someembodiments, separate events are used for Power Up, Power Down, Fan Up,and Fan Down events.

Selected BMC Command Details

BMC commands are generally sent by the CM to determine information orstatus regarding pluggable modules, or to effect a change inconfiguration or status of pluggable modules. BMC commands may bedirected to BMCs on any type of pluggable module (such as a SIM, PMM,NM, FCM, and OLB), via the separate TCP connections for each moduleestablished at module boot. In some embodiments the TCP connections arealso used to communicate BMC events.

Some commands are specific to one module type (such as a PMM), and othercommands may be applicable to more than one module type (such as anymodule including a VIOC, or any module having a configurable powersupply). Typically commands directed toward a SIM are directed to aRedundant SIM by a Primary SIM, since the CM typically executes at leastin part using computing resources included in a Primary SIM (such asPrimary SCM 140A of FIG. 2).

Each BMC command generally includes a command parameter data structuredefining specific details or values associated with the command. Thedata structure typically includes fields identifying the pluggablemodule type receiving the command, and the command identifier (ornumber). SIMs, PMMs, NMs, and OLBs, may be identified as pluggablemodule types 1, 2, 3, and 4, respectively, with unknown modulesidentified as module type 0, according to embodiment. In someembodiments, a dedicated packet format is used to convey commandinformation. In some embodiments, processing of a BMC command mayinclude generating a response event (directed to the CM, for example)acknowledging receipt of the command and describing the outcome of thecommand in the form of a return code.

BMC commands specific to BMCs on PMM modules include Module BCT. TheModule BCT command (identifier 0x000F) is used to instruct the BMC toconfigure the associated PMM (or a previously partitioned portion of it)according to a BCT (provided as a command parameter data structure), andis typically issued in the context of provisioning a server. The BMCparses the provided BCT to determine if the configuration is valid forthe PMM in which the BMC is included. If the configuration is valid,then the BMC configures components on the PMM according to theconfiguration.

The parameters include structures for general, server, VNIC, boot,partition, console, and OS information. The general parameter structureincludes a table version number (such as 0), and an action identifierdescribing an action to take based on the configuration information(such as provision identified by the value 1, and release or reclaimprovision identified by the value 2). The general parameter structurefurther includes a count of the number of BMCs involved in applying theconfiguration (one BMC for a 2-way or a 4-way configuration, and twoBMCs for an 8-way configuration). The general parameters further includean IP address identifying a master BMC associated with theconfiguration, and a list of IP addresses for all of the BMCs involvedin the configuration.

The server structure includes a server type identifier (having valuessuch as 1 for 2-way, 2 for 4-way, and 3 for 8-way), and a slot numberand valid bit to associate with the provisioned server (having valuessuch as 0 and 1). The server structure further includes a system numberand valid bit to associate with the provisioned server (having valuessuch as 0 and 1), and a boot method identifier (such as 1 for networkbooting and 2 for local fibre channel booting). The server structurefurther includes a count of VNICs for the server (from 1 to 64, forexample), a VNIC structure for each of the VNICs, and a list and countof fibre channel boot paths. Each VNIC structure includes a VNICidentifier that is unique throughout the server (such as a 32-bitinteger), a bandwidth specification, and a MAC address for the VNIC.Each fibre channel boot path includes a port identifier of an associatedfibre channel port, a world wide name of a fibre channel destination,and a logical unit number for the fibre channel destination.

The partition structure includes a boot policy identifier (such as 1 for‘Wait-for-SIM’, 2 for ‘autoBoot’, 3 for ‘oneShot’ and 4 for ‘Debug’),and a sticky bit to indicate if the configuration remains over reboots(such as 0 for not sticky and 1 for sticky). The console structureincludes information describing a baud rate, a number of data bits, aparity type, a number of stop bits, and a console type (such as 1 forVT-100). The OS structure includes an OS identifier (such as 1 for Linuxand 2 for Windows).

Processing performed in response to the Module BCT command analyzes theBCT and configures PMM HW accordingly. For example, when the action isto provision a server (action identifier equal to 1), the server typeidentifier is decoded to determine how to configure the HT links on thePMM. More specifically, if the server type is 2-way (type identifierequal to 1), then in the context of PMM 150A (FIG. 4B), HT couplings460.5L and 460.5R are configured for coherent operation by BMC 402.5,and HT couplings 460.5X and 460.5Y are configured for isolatedoperation. If the server type is 4-way (type identifier equal to 2),then HT couplings 460.5L, 460.5R, 460.5L′, 460.5R′, 460.5X, and 460.5Yare configured for coherent operation. The MAC address in each VNICstructure is stored into corresponding configuration state in one ormore VIOCs, such as setting MAC Address 603.1 (FIG. 6A), by writingcorresponding configuration state implemented in VIOC Configurationblock 706 (FIG. 7A).

The response event generated upon completion of the Module BCT commandincludes a return code selected from the set including Valid BCTConfiguration Successful (encoded as 0x0000), Invalid Slot Information(0x0100), Valid BCT Configuration Failure (0x0200), and Invalid BCT(0x0300). Valid BCT Configuration Successful is returned when the BMChas determined that the provided BCT is valid for the associated module,and the specified configuration has been successfully applied to themodule (or portion thereof). Valid BCT Configuration Failure is returnedwhen the BCT is valid but the configuration has not been successfullyapplied. Invalid Slot Information is returned when the slot informationin the BCT is not valid for the module. Invalid BCT is returned when theBMC determines that the BCT is not valid for the module (no attempt ismade to configure the module).

BMC commands specific to BMCs on pluggable modules including VIOCs (suchas SIMs, PMMs, FCMs, and OLBs) include Module Reset VIOC. The ModuleReset VIOC command (identifier 0x000E) causes the BMC to reset aselected VIOC on the module (without resetting any other elements) andis typically issued in response to a request by a VIOC Driver to reset aVIOC. The parameters include a slot number, and a VIOC number to selectwhich VIOC on the module to reset (such as 0 or 1). The return codesinclude VIOC Reset Successful (0x0000), Invalid Slot Information(0x0100), Invalid VIOC Number (0x0200), and VIOC Reset Failure (0x0300).

BMC commands specific to BMCs on pluggable modules having system orapplication processing elements include Module Reset Partition, ModuleHold Reset, Module Release Reset, Module Boot, Module Firmware Update,and Module Firmware Update Status. Such modules include PMMs (havingCPUs), NMs (having PCEs and TMs), FCMs (having IOPs), and OLBs (havingCPUs).

The Module Reset Partition command (identifier 0x0006) causes the BMC toassert and then release reset for an entire module or a partition of amodule (such as a partition of a PMM). If the module has been previouslyconfigured into partitions (by a Module BCT command, for example), thenthe command operates on a specified partition of the module. If themodule is a partitionable module (such as a PMM) and there has been noprevious partitioning of the module, then the entire module is reset andan error is returned.

The parameters include a slot number and a partition identifier. Theassociated return codes include Reset Partition Successful (0x0000),Invalid Slot Information (0x0100), Invalid Partition (0x0200), and ResetPartition Failure (0x0300). Reset Partition Successful is returned whenthe partition identifier is valid and reset has been successfullyapplied and released. Invalid Slot Information is returned when the slotinformation is not valid for the module (for example when the module isinserted in a different slot than the command was intended for, or anincorrect BMC received the command) Invalid Partition is returned whenthe partition identifier is incorrect for module. In some embodiments,Invalid Partition is returned when the module has not been previouslypartitioned (although the entire module is also reset).

The Module Hold Reset command (identifier 0x0005) causes the BMC tobegin asserting reset to system and application processing elements onthe module, a selected partition of the module, or a CPU sub-system onthe module, and to continue asserting reset until a command to releasereset is received. If the module has not been previously partitioned (oris not partitionable), then the entire module (or CPU sub-system) isreset and continues to be reset. The parameters include a slot numberand a partition identifier. The return codes include Hold ResetSuccessful (encoding 0x0000) for indicating the partition identifier isvalid (or ignored) and reset has been successfully applied, Invalid SlotInformation (0x0100),), Invalid Partition (0x0200), and Hold ResetFailure (0x0300).

The Module Release Reset command (identifier 0x0004) causes the BMC tostop asserting reset to system and application processing elements onthe module, a selected partition of the module, or a CPU sub-system onthe module. Typically the Module Release Reset command enables themodule (or the selected partition or CPU sub-system) to boot. It may beused, for example, when directed to a PMM as in “Release Reset Flow”1314S (FIG. 13B). The parameters include a slot number and a partitionidentifier. The return codes include Release Reset Successful (encoding0x0000), Invalid Slot Information (0x0100), and Release Reset Failure(0x0200).

The Module Boot command instructs the BMC to power up, reset, andrelease reset to system and application processing elements on themodule, a selected partition of the module, or a CPU sub-system on themodule. The Module Boot command typically enables the module (or theselected partition or CPU sub-system) to proceed from being not poweredto a fully booted state without additional BMC commands The parametersinclude a slot number and a partition identifier. The return codesinclude Boot Successful (encoding 0x0000), Invalid Slot Information(0x0100), and Boot Failure (0x0200). In some embodiments, intermediateevents return information as the module proceeds through various stagesof executing the Module Boot command.

The Module Firmware Update command (identifier 0xFFFE) instructs the BMCto download and program firmware into non-volatile memory (such as flashmemory) on the module. Downloading typically uses the Trivial FileTransfer Protocol (TFTP). The parameters include an IP address (inbinary format) and a number and list of file names. The return codesinclude Firmware Update Successful (encoding 0x0000), indicating all ofthe requested files have been downloaded and stored into thenon-volatile memory, and Firmware Update Failure (0x0100), indicatingotherwise.

The Module Firmware Update Status command (identifier 0xFFFF) instructsthe BMC to provide information concerning the most recent ModuleFirmware Update command In some embodiments, there are no parameters.Multiple return codes are provided in response, including an overallstatus indicator, a stage indicator, and a completion/an errorindicator. The overall status indicator states include Success (encoding0x0000) and Failure (0x0100). The stage indicator states include UpdateComplete (0), Update Downloading (1), and Updating Flash (2). Thecompletion/error indicator states include percent completion from 0% to100% (encodings 0x00 to 0x64), Update Successful (0x70), No TFTP Server(0x71), File Not Found (0x72), Checksum Invalid (0x73), Bad SectorNumber (0x74), TFTP Connection Closed (0x75), and Canceled (0x76).

Other BMC commands include Module Get VPD, Module SIM Fabric Port,Module Power Up, Module Power Down, Module Get Sensors, Module GetSensor Information, Module Get Operational Status, and Module ForceFault. The Module Get VPD command (identifier 0x0002) causes the BMC tocollect and report information describing the capabilities of themodule. The parameters include a slot number. The return informationincludes several fields and structures, including a status code, a tableidentifier, a count of table entries, a variable number of tableentries, an end marker tag, and a checksum. The status codes include VPDRetrieval Successful (0x0000) and VPD Retrieval Failure (0x0100). Thetable identifier is an 8-bit field in some embodiments. The count oftable entries specifies the number of individual VPD table entries thatfollow the count. The end marker tag (encoded as 0x79) marks the end ofthe VPD table. The checksum is used to verify integrity of the responsedata, and is an 8-bit field in some embodiments.

In some embodiments, VPD entries are compatible with those described bythe Conventional PCI v2.2 Specification, available fromhttp://www.pcisig.com, and hereby incorporated by reference herein forall purposes. Each VPD table entry includes an entry beginning markertag (0x90) followed by a count of fields in the entry and a variablenumber of fields as indicated by the count. Each field in turn includesa field name (a 3-character string in some embodiments), a field length,and a field value string having a length as indicated by the fieldlength. The general format of the VPD table enables essentiallyunlimited information to be provided by the BMC to the CM, as the formatis not restrictive.

The VPD returned may vary according to module and embodiment. In someembodiments, and for some modules, VPD may include descriptions ofnumber and capabilities of system and application processing elementspresent on or associated with the module. Examples include number andfrequency of CPUs included on PMMs, PCEs and TMs included on NMs andincluded on daughter cards coupled to NMs, IOPs included on FCMs, CPUsincluded on OLBs, and CPUs and Accelerators included on daughter cardscoupled to OLBs. VPD may include memory size and organization on themodule. VPD may include MAC address information associated with themodule, such as a MAC address associated with a VIOC on the module.

VPD returned for SIM modules may indicate the presence and capabilitiesof Mass Storage 412A (FIG. 4A), and information concerning PrimarySwitch Fabric Module 180A. VPD returned for PMM modules may indicate thepresence and capabilities of FCI 413.5 and FCI 413.5′ (FIG. 4B). VPDreturned for NM modules may describe Interface 420 and IOP 421 (FIG.4C), including bandwidth capacity and physical interface type. VPDreturned for FCM modules may describe operational parameters associatedwith FCPs, such as FCP 423.4 (FIG. 4D). VPD returned for OLB modules maydescribe the presence and capabilities of optional daughter cards ormodules, such as PCI sub-module 425 and HT sub-module 424 (FIG. 4E),including descriptions of specific services or protocols accelerated bythe daughter elements. The aforementioned module-specific VPDinformation may vary in specific details and may be provided in variouscombinations, according to embodiment.

The Module SIM Fabric Port command (identifier 0x000D) informs the BMCof the physical fabric port number of the Primary SIM (having anincluded Primary SCM), such as the fabric port associated with PrimarySCM-Fabric coupling 149A (FIG. 2) as coupled to Primary Switch FabricModule 180A. The parameters include a slot number and a fabric portnumber. The fabric port number corresponds to the fabric port number ofthe primary (or master) SIM of the chassis (such as 4 or 5). The returncodes include SIM Fabric Port Success (0x0000) and SIM Fabric PortFailure (0x0100). In some embodiments, SIM Fabric Port Failure isreturned when the BMC fails to register the SIM fabric port.

The Module Power Up and Module Power Down commands (identifiers 0x0003and 0x007, respectively) instruct the BMC to apply and remove,respectively, operating power for the remainder of the module. TheModule Power Up command leaves reset to system and applicationprocessing elements of the module asserted. The Module Power Downcommand optionally fails unless the module (such as a PMM) has nobooted, active, or running partitions, or has no active heartbeatestablished, according to embodiment. The parameters include a slotnumber. The return codes include Success (0x0000), Invalid SlotInformation (0x0100), and Failure (0x0200).

The Module Get Sensors command (identifier 0x000A) causes the BMC toreturn information regarding sensors available on the module, such asthe number and types of sensors. The parameters include a slot number.The return information includes a status code, a count of sensorsavailable, and a variable number of sensor identifiers. The status codesinclude Success (0x0000), Invalid Slot Information (0x0100), and Failure(0x0200). The count of sensors specifies the number of sensors availableon the module and individually identified by the information followingthe count. Each of the sensor identifiers is a 32-bit integer in someembodiments.

The Module Get Sensor Information command (identifier 0x000B) causes theBMC to return information about a selected sensor or list of sensors, asspecified by the command The parameters include a slot number, a countof sensors requested, and a variable number of sensor identifiers. Thecount of sensors requested specifies the number of sensors for whichinformation is requested and individually identified by the informationfollowing the count. Each of the sensor identifiers is a 32-bit integerin some embodiments. The return information includes a status code, anda sensor information structure for the sensors selected by the sensoridentifiers. The status codes include Success (0x0000), Invalid SlotInformation (0x0100), and Failure (0x0200). In some embodiments, sensorinformation structures are compatible with IPMI v1.5, available fromftp://download.intel.com/design/servers/ipmi/IPMIv1_(—)5rev1_(—)1.pdf,and hereby incorporated by reference herein for all purposes. Each ofthe sensor information structures includes a sensor identifier (32-bits,for example), a length specification (16-bits, for example) equal to thelength of the following name, value, and type fields (including nulls),a name string, a value string (representing the current value of thesensor), and a data type field for the value string.

The Module Get Operational Status command (identifier 0x000C) instructsthe BMC to return the operational status of a module or a selectedpartition of a previously partitioned module (such as a PMM). Typicallythe operational status is determined by the presence of a heartbeatbetween the BMC and an OS (or BIOS) executing on the module or theselected partition. The parameters include a slot number and a partitionidentifier. The return information includes a status code and anoperational code. The status codes include Get Operational StatusSuccessful (0x0000), Invalid Slot Information (0x0100), InvalidPartition (0x0200), and Get Operational Status Failure (0x0300). Theoperational codes include Down/Non-operational (0x0000) andUp/Operational (0x0100).

In some embodiments, The Module Force Fault command instructs the BMC toforce the BMC Operational State Machine associated with the module (or aselected partition of a module) to transition to state F 1306 (FIG.13A), and may be used when the CM detects operational errors requiringthe module to be failed. The parameters may include a slot number and apartition identifier, according to embodiment.

Other BMC commands are IPMI-compliant, and relate to collecting andmanaging information in a System Event Log (SEL) maintained by a BMC,and include Module Get SEL and Module Clear SEL. The Module Get SELcommand causes the BMC to provide selected log entries from theassociated SEL. The parameters include a slot number, an offset, and amaximum count. The offset specifies a starting point in the SEL fromwhich the BMC is to return data, to prevent resending older data. Themaximum count specifies the maximum number of entries to provide in thereturn information.

The return information includes several fields and structures, includinga status code, a count of returned log entries, and a variable number oflog entries. The status codes include Get SEL Successful (0x0000),Invalid Slot Information (0x0100), Invalid Offset (0x0200), and Get SELFailure (0x0300). The count of log entries specifies the number ofindividual log entries that follow the count. Each returned log entry,in some embodiments, includes a 16-byte field encoded according to anIPMI standard (such as is described on page 308 of IPMI specificationRev 1.1, incorporated herein by reference for all purposes).

The Module Clear SEL command (identifier 0x0009) causes the BMC to clearall or selected log entries from the associated SEL, according toembodiment. The parameters include a slot number. The return codesinclude Clear SEL Successful (0x0000), Invalid Offset (0x0200), andClear SEL Failure (0x0300).

In some embodiments, the aforementioned command identifiers varyaccording to target module. For example, a prefix may be insertedidentifying the module type (such as 0x0001 for SIMs, 0x0002 for PMMs,and 0x0003 for NMs, according to embodiment). In some embodiments, theaforementioned return codes are 16-bit values, and the status codes are8-bit values. In some embodiments, the slot number is 0 or 1 for PMMs, 2or 3 for SIMs, 4, 5, or 6 for NMs, and other values for other modules.In some embodiments, the partition identifier is 0 or 1 to select afirst or a second partition of a PMM that is partitioned as a 2-wayelement. In some embodiments, the partition identifier is optional, andis provided only for a command directed to a PMM. In some embodiments(or contexts, such as a PMM), the partition identifier is ignored unlessthe module has been partitioned as a 2-way element.

Those of ordinary skill in the art will recognize that specifics relatedto BMC event and command communication, such as specific encodings,field sizes, and organization of structures, may vary according toembodiment.

Chassis Manager Operation

This section provides additional information on selected aspects of someembodiments of the CM. Typically the CM provides a single source ofchassis information to all other processes in the system. It providesother processes with information such as presence of modules, propertiesof the modules and status of the modules. It also provides informationabout failure of modules and changes in module configurations. Toprovide such detailed information about each of the modules, the CMpeers with the BMC on each of the modules in a chassis and obtains vitaldata to maintain a persistent database.

The CM may be considered to provide a window into an ES systemembodiment and an interface to users and operators to view and modifyvarious system level behaviors. Typically there is a plurality of slots(10, for example) in an ES system chassis embodiment. In someembodiments, each slot in the chassis is enabled to accommodate only onetype of pluggable module. In these embodiments, the slot assignments andthe module types in the chassis are predefined.

At startup (or ES system boot) the CM performs various initializationsteps, including resetting values of global variables, initializing anevent library, and initializing the BMC interface of the SCM the CM isexecuting on. Typical SCM embodiments include a Mastership Module (MM),and the CM initializes an interface of the MM. The CM then issues aProcess Initialized Event.

The initialization of the various interfaces triggers an associated setof activities in the CM. The CM performs the initialization functionsand then enters a loop for listening to events occurring in the system,such as those reported by the Module BMC SW.

The MM is typically implemented in all or a portion of an FPGA,according to embodiment, and provides various functions, also accordingto embodiment. The functions may include an application level heartbeat,and an identification of the slot that the SCM the CM is executing on isinserted. Other functions may include presence information of variousmodules inserted in the chassis, notification of pluggable moduleinsertion (such as that associated with “Detect Module Insertion andGenerate Presence Interrupt” 1201.2 of FIG. 12A), and notification ofpluggable module removal. Further functions may include variousindications of whether or not inserted modules are capable of poweringup and powering down. Further functions may enable failover from aPrimary SCM to a Redundant SCM (such as the Primary and Redundant SCMs140 of FIG. 1A), either manually via a user or operator request, orautomatically as a result of a system failure.

In some embodiments, the MM includes a Mastership state machine. Inoperation, the CM indicates it has booted, and in response the statemachine transitions from a Waiting state to a Booted state. In theBooted state, the state machine determines whether the SCM the CM isexecuting on is a Primary SCM or a Secondary SCM, and transitions to aPrimary or Redundant state accordingly.

In the Booted state, the SCM is determined to be the Primary SCM ifthere is currently no Primary SCM, and otherwise it is the RedundantSCM. If the determination of Primary versus Secondary roles is notpossible, then an error is recognized and the state machine transitionsto an Error state. If there is a failover (either manually orautomatically) then a transition is made from the Redundant to thePrimary state, and the SCM becomes a new Primary SCM and the CM changesroles from Redundant to Primary accordingly.

During initialization the CM also sets a watchdog time interval in theMM, corresponding to a heartbeat for SW executing on the SCM. The CMsets a watchdog bit at regular intervals (shorter than the watchdog timeinterval). If the CM is unable to set the watchdog bit within thetimeout of the watchdog interval, then the MM assumes that the SWexecuting on the SCM is locked up and the SCM becomes unavailable. Ifthe SCM is the Primary SCM, then an automatic failover occurs, and theRedundant SCM becomes a new Primary SCM. If the SCM was the RedundantSCM, then the SCM is no longer available for failover, and there is nolonger a Redundant SCM.

When an SCM becomes a Primary SCM, the CM reads the identification ofthe SCM slot from the MM and stores it in an internal variable. The CMthen obtains the presence information from the MM (such as by readingselected MM registers, in some embodiments) and determines the modulesthat are present in the chassis. The CM then populates a database ofmodules (such as Primary CIM Instance Repository 917.P of FIG. 9C) andattempts to set up communication channels with BMCs on each of themodules that were indicated as being present.

When a module is added or removed from the chassis, the MM detects thischange and notifies the CM via an event. The CM receives the event,determines the affected slot, and carries out any necessary actions asdetermined by the specific module involved. There is also a notificationwhen the SCM has changed from Secondary to Primary (such as duringfailover processing).

In some embodiments, the CM maintains a map of the slots in the chassis.In some embodiments, the slots are restricted to selected modules (forexample, PMMs may only be inserted in slots 0 or 1, SIMs in slots 2 or3, NMs in slots 4, 5, or 6, and so forth according to embodiment). Insome embodiments, the map includes information concerning the type ofmodule that may be inserted in each slot according to the restrictions.The module type information may vary according to any combination ofproduct type, chassis type, or other similar customization information,according to various embodiments.

The CM attempts to establish a TCP connection for each module in thechassis by issuing a connect request to the BMC on each respectivemodule. In some embodiments, the request issuing is non-blocking andarrives asynchronously. As each connection is established, the CMtypically requests VPD for the corresponding module (using a Module GetVPD command, for example). Returned information arrives via acorresponding BMC event, and is processed and stored in the moduledatabase. The information is used, for example, to determine a moduletype and various properties associated with each respective module.

Once the VPD information has been collected and processed into thedatabase, the CM issues module presence events to any other processesthat may be listening for the module presence events. In someembodiments, the presence is published (i.e. module presence eventsgenerated) only if the VPD information is obtained. If there is afailure in retrieving the VPD data, then the module is considered of anunknown or unrecognized type.

The CM then collects other information such as module properties, sensorproperties and anything else that may be necessary for CM and relatedfunctions. The CM may also poll the SEL maintained by the BMC todetermine if there were any new system events logged. System events inthe SEL may also be dumped into a system log file along with appropriateinformation to identify sources of the dumped system events.

When a module is prepared to boot, the CM may initiate booting byissuing a command (such as a Module Boot or a Module BCT command) to theBMC of the module. The CM also initiates module resets, reloads, andother related operations by issuing corresponding BMC commands. Thevarious commands from the CM to the BMCs may be results of manual userinput or automatic provisioning or configuration processing.

The CM stores module information (such as presence, sensor values, andso forth) in the database. Thresholds and policies relating to thesevalues may also be stored in the database, and in some embodiments areimplemented as queries having corresponding actions.

In some embodiments, booting of some pluggable modules that includesystem or application processing elements (such as PMMs, NMs, FCMs, andOLBs) includes providing one or more data images to the booting module.In some embodiments, after the CM has received VPD from the module, theCM updates a Dynamic Host Configuration Protocol (DHCP) configurationfile and creates or updates a Pre-boot eXecution Environment (PXE)configuration file for the module. The CM then restarts a DHCP daemonand issues a BMC command to boot the module. The module subsequentlyissues a DHCP request, and the DHCP daemon responds with IP address andPXE configuration information, according to the updates the CM hasperformed. The module then requests a kernel image and RAM disk imagevia TFTP, the images are transferred, and the module boots using theimages.

Since the DHCP configuration file is accessed during module boot, andmodules may be dynamically configured in or added to live systems andthen booted, the CM must dynamically alter the DHCP and PXE informationas module configuration changes, or as modules are inserted into thechassis. Additionally, in these embodiments, the DHCP configuration filemay also include entries corresponding to each of the bootable modules.In some embodiments, the VPD includes a MAC address, and the CM maydetermine some portion of DHCP and PXE configuration information basedin part on the MAC address. In some embodiments, the configurationinformation may also be based in part on processing of an SCF whenperforming an install server command (such as “Installing” 1103 of FIG.11).

In some embodiments, the CM stores portions of configuration data andportions of runtime information, including portions of the database, inthe form of CIM instances, providing a standard interface for queryingthe information and other operational parameters. In some embodiments,Chassis Manager 533 may issue events to Repository Manager 535 to createCIM instances corresponding to modules inserted in the chassis, forexample when VPD is returned and processed. Additional CIM instances maybe created to represent components of inserted modules. In someembodiments, creation and maintenance of the CIM instances (or instancesof classes) may be performed in a library form in a platform process(such as a process associated with Platform Manager 531).

In some embodiments, commands or requests originating from CLI and GUIoperations trigger the CM to carry out operations necessary to performthe requested command The operations may include accessing the databaseto view CIM instances (corresponding to modules or components in thechassis), and delivering BMC commands as needed. The operations mayfurther include updating CIM instances as module state changes, asindicated by received BMC events. Some of the BMC events may begenerated due to processing the BMC commands, and may indicate successor failure of a command This enables a user to determine success orfailure of a request by requesting a display of appropriate modulestatus information.

In some embodiments, asynchronous requests are posted to the CM withoutblocking, and a requestor determines success or failure by specificallyrequesting status from the CM. In some embodiments, synchronous requestsare posted to the CM with blocking, and wait for status returned fromthe CM before completion.

In some embodiments, one or more processes associated with anycombination of Enterprise Manager 530 and Platform Manager 531 mayrequire portions of module sensor information (and portions of othermonitoring information) to be visible via CIM instances. In someembodiments, the CM acts as the instance provider for some or all of thesensor and monitoring instances, creating the instances as correspondinginformation is received (perhaps in response to commands) from themodules. In some embodiments, all non-configuration type CIM instancesare managed in the CM context (the CM performs as the associatedinstance provider) and all configuration type CIM instances are managedby Platform Manager 531.

The embodiments described in the Chassis Manager Operation section areillustrative only, as those of ordinary skill in the art will recognizethat selected CM functions may be performed elsewhere while still underthe direct control of the CM. Additionally, some of the functions may bemodified, added, or deleted, according to embodiment.

Rapid IP/MAC Address Takeover

Layer-3 and above networking protocols typically identify and namesources, destinations, and resources using one or more IP addresses, andthe IP addresses are mapped to associated MAC addresses while performingvarious switching and routing functions. A pluggable module of an ESsystem embodiment is typically associated with (or assigned) one or moreIP addresses, such as Public IP Address 604.1 (FIG. 6A), and one or moreMAC addresses, such as MAC Address 603.1. IP and MAC addresses aretypically assigned or configured when a server is provisioned (see theServer Operational States section, elsewhere herein). For modules havingVIOCs implementing one or more VNICs, appropriate values are writteninto each of the respective public IP and MAC address registerscorresponding to the assignments.

Layer-3 forwarding information (including correspondence betweenselected IP addresses and respective MAC addresses) is maintained bysystem management, controlplane, and load balancing processes (alsoreferred to collectively as “SCM processes” since they are executed byan SCM that is part of a SIM). In some embodiments, the SCM processesprovide portions of the layer-3 forwarding information to pluggablemodules, typically as L3 FIB updates. For example, in some embodimentsNMs include search engines accessing IP to MAC forwarding informationthat is managed by the SCM processes, and in some embodiments VIOCsaccess forwarding information (stored in coupled TCAM/SRAMs) that isalso managed by the SCM processes.

Layer-2 networking protocols typically communicate source anddestination information using MAC addresses, and pluggable modules in anES system embodiment typically map each pluggable module MAC address toa corresponding fabric port address. The correspondence between moduleMAC addresses and fabric port addresses is maintained by the SCMprocesses, according to embodiment, and may be modified when a server isprovisioned. The MAC address to fabric port address mapping (orforwarding) information is typically provided to pluggable modules,typically as L2 FIB updates. For example, in some embodiments the NMsearch engines access and manage a cache of MAC to fabric portforwarding information that is provided by the SCM processes. In someembodiments, VIOCs access and manage a cache of similar forwardinginformation (such as MACFIB information as discussed in the TCAM/SRAMLookup State section, elsewhere herein) that is also managed by the SCMprocesses.

In some embodiments, server provisioning and management functions enabledetection of a failed module, identification of a standby module(already available in the system), and automatic failover replacement ofthe failed module by the standby module. According to variousembodiments, any combination of the IP address and the MAC addressassigned to the failed module are re-assigned to the standby module.Consider an illustrative scenario such that before the failure, themodule that is going to fail is associated with a first IP address and afirst MAC address, and such that the standby module is associated with asecond IP address and a second MAC address. Also consider that there maybe an optional mapping between a service provided by the module that isgoing to fail and a service IP address, such that before the failure theservice IP address is equal to the first IP address.

In a first group of takeover embodiments, where only the IP address isre-assigned, the standby module is associated with the first IP address(replacing or “taking over” the first IP address) as part of performingthe module failover. The standby module remains associated with thesecond MAC address, and thus the first IP address should no longer beresolved to the first MAC address, but to the second MAC address. Insome implementations, an Address Resolution Protocol (ARP) compatibleaddress discovery mechanism is used to discover the new mapping when theremapped IP address is referenced. The new mapping is then propagated tothe layer-3 forwarding information tables (such as those accessed by theNM search engine and the VIOCs, according to embodiment). In otherimplementations, the SCM processes intercede during the ARP-compatibleprocessing, recognizing a “local” IP address and providing acorresponding local MAC address without overheads typically associatedwith ARP-compatible processing. Local IP addresses include IP addressesallocated to pluggable modules (such as SIMs, PMMs, NMs, FCMs, and OLBs)within an ES system or within an ES chassis. In still otherimplementations, the SCM processes actively update the new mapping inthe layer-3 forwarding information tables upon the replacement event,irrespective of if or when the remapped IP address is referenced. Sincethe MAC addresses are unchanged in the first group of embodiments, thelayer-2 forwarding information (such as mappings to fabric portaddresses) is also unchanged. If there is a mapping between the serviceand an associated service address, then since the standby module hasbeen assigned the first IP address, no change in the service address ismade.

In a second group of embodiments, where only the MAC address isre-assigned, the standby module is associated with the first MAC address(taking over the first MAC address) as part of performing modulefailover. The second group of embodiments is typically used inconjunction with local service IP addresses (i.e. the service address isnot visible external to the ES system), or in conjunction with a proxy,or in circumstances where changes to the service address areinconsequential. The standby module remains associated with the secondIP address, and thus the mapping between the first IP address and thefirst MAC address is no longer valid, and a new mapping between thesecond IP address and the first MAC address is created. As in the firstgroup of embodiments, some implementations use the ARP-compatiblemechanism and some implementations use the active update of the newmapping. Since the MAC address is changed, the layer-2 forwardinginformation is also changed accordingly, and the SCM processes activelypropagate new MAC to fabric port address mapping information to thepluggable modules. If there is a mapping between the service and anassociated service address, then since the standby module is assignedthe second IP address, the service address is changed to the second IPaddress. Some implementations perform passive discovery of this newmapping via the ARP-compatible mechanism and some implementations usethe active updating of the new mapping.

In a third group of embodiments, where both the IP and the MAC addressesare re-assigned, the standby module is associated with the first IPaddress and the first MAC address as part of performing module failover.The mapping between the first IP address and the first MAC addressremains valid, however the layer-2 mapping between the first MAC addressand the associated fabric port is updated, and the associated layer-2forwarding information is changed by active propagation to the pluggablemodules. If there is a mapping between the service and an associatedservice address, then since the standby module has been assigned thefirst IP address, no change in the service address is made.

FIG. 14 illustrates a conceptual view of selected aspects of embodimentsof IP and MAC address failover data structures and associatedoperations, including HW elements 1404 and IP/MAC Address and ForwardingChart 1405. Three techniques are illustrated, corresponding to oneembodiment of each of the aforementioned three groups of embodiments.

For clarity, the illustrated HW elements include only selected portionsof an ES system embodiment, Primary Switch Fabric Module 180A providingcommunication between included modules NM 130B, Primary SCM 140A, PMM150A, and PMM 150B. The NM includes Search Engine 1406 to search stateinformation included on the NM to perform layer-3 forwarding functions,including supplying a forwarding MAC address for a provided IP address.The SCM executes the SCM processes. PMM 150A illustrates a “failure”PMM, in other words a PMM that is initially functioning properly, butthen becomes non-functional. PMM 150B illustrates a “standby” PMM, inother words a PMM that is initially unused (or spare), but is later usedto replace the failed PMM. Each of the PMMs includes a VIOC (301.5 and301.5B) and a TCAM/SRAM (403.5 and 403.5B) accessed in part for layer-2and optionally for layer-3 forwarding functions, according to variousimplementations.

IP/MAC Address and Forwarding Chart 1405 illustrates address andforwarding information before PMM 150A fails, and correspondinginformation after PMM 150B has replaced PMM 150A, for each of the threetechniques. The chart is organized in rows and columns. “Initial MAC/IP”column 1410 shows information before the failure, and “Technique 1MAC/IP” column 1411, “Technique 2 MAC/IP” column 1412, and “Technique 3MAC/IP” column 1413 show final information after failure processing forthe three techniques.

Failure PMM Address Row 1420A and Standby PMM Address Row 1420B show IPand MAC address information stored in VIOCs 301.5 and 301.5B included inPMMs 150A and 150B respectively, for the initial and final states. Morespecifically, the failure and standby IP address information are storedin respective instances of Public IP Address 604.1 (FIG. 6A),corresponding to VNICs implemented in VIOCs 301.5 and 301.5B. Thefailure and standby MAC addresses are stored in respective instances ofMAC Address 603.1.

MAC to Fabric Port Forwarding Rows 1430 shows destination MAC address todestination fabric port address forwarding information stored inTCAM/SRAMs 403.5 and 403.5B and referenced by VIOCs 301.5 and 301.5Brespectively. More specifically, 1430 shows key and result pairs asdescribed in association with FIG. 8B. For example, instances of EgressKey 801 are programmed with MAC addresses as shown in 1430 (MAC1 andMAC2), and corresponding Unicast Result 803 instances are programmedwith DstFabAddr 811 as shown in 1430 (FPort0 and FPort1). Typicallyidentical information is stored in TCAM/SRAMs 403.5 and 403.5B, suchthat both VIOC 301.5 and VIOC 301.5B have access to the same mappings.IP to Fabric Port Forwarding Rows 1431 show destination IP address todestination fabric port address forwarding information referenced bySearch Engine 1406. Service Address Row 1432 shows an IP addressassociated with a service provided by PMM 150A before failing, and byPMM 150B after completion of failover processing. In someimplementations the IP address to service mapping of 1432 is alsoreferenced by Search Engine 1406.

In the subsequent discussion the terminology “address(es) stored in PMM”is shorthand for “address(es) stored in a VNIC implemented in a VIOCincluded in PMM”. The shorthand terminology is meant to refer to storagein an instance of Public IP Address 604.1 for an IP address, and tostorage in an instance of MAC Address 603.1 for a MAC address.

Initially, as illustrated by the chart (“Initial MAC/IP” column 1410),the IP address stored in PMM 150A (the PMM that is to fail) is IP1, andthe MAC address stored in PMM 150A is MAC1. The corresponding initialaddresses stored in PMM 150B (the standby PMM) are IP2 and MAC2. Theinitial MAC address to fabric port forwarding information stored in theTCAM/SRAMs of both PMM 150A and PMM 150B associates MAC address MAC1 (ofPMM 150A) with fabric port 0 (FPort0, corresponding to slot 0), and MAC2(of PMM 150B) is associated with fabric port 1 (FPort1, corresponding toslot 1). The initial IP to fabroic port address forwarding informationreferenced by Search Engine 1406 associates IP1 to FPort0 and IP2 toFPort1. The initial mapping for the service is to IP address IP1 (thatof PMM 150A).

After a failover processed according to the first technique (an IPtakeover as in the first of the aforementioned groups of embodiments),the IP address stored in PMM 150B (the standby PMM that has replaced thefailed PMM) is set to the value of the IP address previously stored inPMM 150A (the failed PMM). This is illustrated by PMM_B IP address 1450(of “Technique 1 MAC/IP” column 1411) having the value IP1. The IP andMAC address information stored in the VIOC of PMM 150A (the failed PMM)is no longer relevant, as the module is no longer being used. The IP tofabric port address forwarding information has changed, since thereplacement module has taken on the IP address of the failed modulewithout also taking on the fabric port address of the failed module(i.e. the modules remain in their original slots). This is illustratedby IP to fabric port address entry 1454 having the value FPort1. The MACaddress to fabric port forwarding and service IP address mappinginformation are not changed (see the intersection of rows 1430 and 1432,respectively, with column 1411), as the initial mappings remainapplicable. Note that the MAC address to fabric port forwardinginformation previously associated with MAC1 is no longer valid, as theMAC1 address is no longer being used.

After a failover processed according to the second technique (a MACtakeover as in the second of the aforementioned groups of embodiments),the MAC address stored in PMM 150B (the replacement PMM) is set to thevalue of the MAC address previously stored in PMM 150A (the failed PMM).This is illustrated by PMM_B MAC address 1451 (of “Technique 2 MAC/IP”column 1412) having the value MAC1. As in the first technique, the IPand MAC address information stored in PMM 150A is no longer relevant, asthe module is no longer being used. The MAC address to fabric portforwarding information is changed, since the replacement PMM has a newMAC address but has remained inserted in the same slot. This isillustrated by MAC address to fabric port address entry 1455 (of“Technique 2 MAC/IP” column 1412) having the value FPort1. Withreference to the intersection of column 1412 with row 1430, the MACaddress to fabric port forwarding information associated with MAC2 is nolonger valid, and the MAC1 address is now associated with a differentfabric port address. The IP to fabric port address forwarding associatedwith the IP address of the failed module is now invalid. The service IPaddress mapping has changed, since the replacement module is known by adifferent IP address than the failed module. This is illustrated byservice IP address 1456 having the value IP2.

After a failover processed according to the third technique (both IP andMAC address takeover as in the third of the aforementioned groups ofembodiments), the IP and MAC addresses stored in PMM 150B (thereplacement PMM) are set to the corresponding values previously storedin PMM 150A (the failed PMM). This is illustrated by PMM_B IP address1452 (of “Technique 3 MAC/IP” column 1413) having the value IP1, andPMM_B MAC address 1453 having the value MAC1. As in the first and secondtechniques, the IP and MAC address information stored in PMM 150A is nolonger relevant, as the module is no longer being used. As in the secondtechnique, the MAC address to fabric port forwarding information ischanged, as illustrated by MAC to fabric port address entry 1457 havingthe value FPort1. With reference to the intersection of column 1413 withrow 1430, the MAC address to fabric port forwarding informationassociated with MAC2 is no longer valid, and the MAC1 address is nowassociated with a different fabric port address. As in the firsttechnique, the IP to fabric port address forwarding is changed, asillustrated by IP to fabric port address entry 1458 having the valueFPort1. The service IP address mapping information associated with IP1is not changed, as the initial mappings remain applicable.

FIG. 15 illustrates a flow diagram of an embodiment of rapid IP addresstakeover in a context of replacing a failed module with a standbymodule. An IP address originally associated with a first MAC address(corresponding to the failed module), is re-associated with a second MACaddress (corresponding to the standby module). Although failoverprocessing that directs the re-association is typically executed outsideof the standby module, the re-association is often described as thestandby module “taking over” the IP address from the failed module, andcorresponds to the aforementioned first group of embodiments.

Processing begins at “Start” 1501, and then flows to “Detect FailedModule” 1510 upon determination that a module is no longer functional(such as PMM 150A as shown in FIG. 14). Flow then proceeds to “IdentifyReplacement Module” 1511 to determine a standby module to serve in placeof the failed module (such as PMM 150B replacing PMM 150A). Processingcontinues at “Determine Replacement MAC Address” 1512 where the MACaddress of the standby module is ascertained. This may be performed byconsulting appropriate MAC address assignment or allocation tablesmaintained by the SCM processes, by reading state managed by the module(such as an instance of MAC Address 603.1), or by other similarmechanisms, according to embodiment. Note that this operation isdistinct from determining an IP to MAC address mapping, as there is nospecific IP address involved in “Determine Replacement MAC Address”1512.

The standby module MAC address, and its correspondence to the IP addresspreviously associated with the failed module, is made known throughoutthe SCM processes by updating a master Layer-3 FIB table (“Update MasterL3 FIB” 1513). Flow continues to “Update Module L3 FIBs” 1514, where thecorrespondence between the IP address and the standby module MAC addressis actively disseminated to module tables (such as forwardinginformation consulted by Search Engine 1406), replacing the stalecorrespondence to the failed module MAC address. Typically the SCMprocesses communicate with interface management processes that in turnprovide updates to search engine look up state via the switch fabricmodule. This contrasts to a more passive replacement of IP to MACcorrespondence information for IP addresses external to an ES system(such as Client 103 of FIG. 1A) via Address Resolution Protocol (ARP)requests. Note: as ARP responders, the SCM processes reply to subsequentARP requests for the re-associated IP address with the standby moduleMAC address. Processing is then complete at “End” 1598.

The illustrated embodiment of FIG. 15 is shown determining andpropagating a new IP address to MAC address association (leaving anoriginal IP address for an associated service intact) when replacing afailing module with a standby module (corresponding to theaforementioned first group of embodiments). Some embodiments alsodetermine and propagate a new IP address to fabric port addressassociation in conjunction with propagating a new IP address to MACaddress association. Other embodiments determine and propagate an IPaddress update, or both MAC and IP address updates (corresponding to theaforementioned second and third groups of embodiments, respectively),including propagating updates as appropriate for the following mappings:IP address to MAC address, MAC address to fabric port address, and IPaddress to fabric port address.

In some embodiments, the SCM processes program the Layer-2 and Layer-3module tables (L2 FIBs and L3 FIBs) in their entirety with respect toall elements known to reside within an ES system. For example, withrespect to FIG. 14, all IP and MAC addresses to fabric port addresscorrespondences are programmed into the TCAM/SRAM structures included onthe PMMs and into the search engines included in the NMs. Thepre-programming of mapping information guarantees that references tolocal IP and MAC addresses will be found in the module tables (i.e. willbe “hits”). Subsequently, when IP and MAC takeover occurs (for exampleduring failover processing), the SCM processes update the L2 and L3 FIBsimmediately, guaranteeing that later references to local IP and MACaddresses will continue to be hits in the module tables.

In some embodiments, the L2 and L3 FIB preprogramming is limitedaccording to VLAN configuration but still sufficient to guarantee thatlocal IP and MAC address references are hits, to conserve TCAM/SRAMentry usage. For example, TCAM/SRAM 403.5 would be initiallypreprogrammed only with entries corresponding to the VLANs that VNICsimplemented in VIOC 301.5 were members of, while TCAM/SRAM 403.5B wouldbe initially programmed according to VLAN membership of VNICsimplemented by VIOC 301.5B. Depending on specific VLAN membership ofVNICs, there could be entries uniquely present in TCAM/SRAM 403.5,entries uniquely present in TCAM/SRAM 403.5B, and entries present inboth TCAM/SRAMs 403.5 and 403.5B. Failover processing would immediatelyupdate and add TCAM/SRAM 403.5B entries in order to continue to continueguarantee local IP and MAC address hits.

According to various embodiments, NMs and PMMs may implement anycombination of L2 and L3 FIBs and perform corresponding L2 and L3forwarding lookups. In some embodiments, the L2 and L3 module tables aredistinct, while in other embodiments the L2 and L3 module tables areimplemented in a single combined module table, with L2 and L3 typeentries being differentiated by a table identification field (of one ormore bits) stored in the table and included in the lookup key.

The foregoing discussion focuses on module tables typically implementedas TCAM/SRAM elements associated with VIOCs included on PMMs. However,TCAM/SRAM elements associated with VIOCs included on SCMs, FCMs, andOLBs, as well as TCAM/SRAM elements included on NMs function similarly.Those of ordinary skill in the art will readily appreciate how to extendthe failover techniques to other module types having TCAM/SRAM elementsimplementing Layer-2 and Layer-3 module tables.

Multi-Chassis Provisioning And Management

FIG. 16 illustrates an embodiment of a multi-chassis fabric-backplane ESsystem, also referred to simply as a “multi-chassis system”. Servers maybe provisioned from compute, storage, and I/O resources available viathree chassis (ES 110X, ES 110Y, and ES 110Z), each similar to ES1 110A(see FIG. 1A). Conceptually the multi-chassis provisioning process issimilar to that of a single chassis, as illustrated in FIGS. 9A, 9B, and11 and their respective discussions, except that resources forprovisioning are distributed amongst more than one chassis.

As illustrated in FIG. 16, each chassis includes an SFM (SFM 180X of ES110X, for example) coupled to various compute, storage, and I/O modules.The compute modules include two OLBs (OLB 160XA and OLB 160XB of ES110X, for example), two PMMs (PMM 150XA and PMM 150XB of ES 110X, forexample), and an SCM (SCM 140X of ES 110X, for example). Storage modulesinclude two FCMs (FCM 120XA and FCM 120XB of ES 110X, for example). I/Omodules include two NMs (NM 130XA and NM 130XB of ES 110X, for example).ES 110Y and ES 110Z are similar to ES 110X (similar elements areidentified with a ‘Y’ and a ‘Z’, respectively, in the identifier nameinstead of an ‘X’). Fibre channel standard storage arrays (or networkscoupled to arrays, according to implementation) are coupled to each ESchassis, as illustrated by Fibre Channel Array/Networks 106X, 106Y, and106Z, coupled to ESs 110X, 110Y, and 110Z, respectively.

Each ES system chassis is coupled to LAN/WAN/MAN/Internet network 1619,ES 110X via NM 130XB and coupling 1614, ES 110Y via NM 130YB andcoupling 1615, and ES 110Z via NM 130ZB and coupling 1621. In someembodiments, network 1619 (or similar network interconnectivity reachedvia NMs) provides a majority of communication bandwidth between variouschassis of a multi-chassis system, including communication between theSCMs of the multiple chassis. In some embodiments, additionalconnectivity between SCMs of a multi-chassis system is included, asillustrated by dash-line coupling 1616 between SCM 140X and SCM 140Y,and dashed-line coupling 1622 between SCM 140Y and SCM 140Z. Client1601A is coupled to ES 110X (via coupling 1617 to SCM 140X) and to ES110Z (via coupling 1618 to SCM 140Z). Client 1601B is coupled to network1619 via coupling 1620, and the network provides indirect couplingbetween Client 1601B and SCMs 140X, 140Y, and 140Z.

At least two major variations of multi-chassis provisioning andmanagement operations are possible. A first, or “Master-Free” variation,is illustrated by Client 1601B operating in conjunction with a host SCM(such as any one of SCM 140X, SCM 140Y, and SCM 140Z) executingmulti-chassis management and provisioning operations (such as thoseprovided by Enterprise Manager 530 of FIG. 5B). A second, or“Client-Mastered” variation, is illustrated by Client 1601A operating asa master to two or more SCMs (such as SCM 140X and SCM 140Y), with eachSCM executing single-chassis management and provisioning operations(such as those provided by CM 533). The two variations are described inmore detail with respect to FIG. 17.

The illustrated embodiment shows couplings 1617 and 1618 coupling Client1601A to SCM 140X of ES 110X and SCM 140Z of ES 110Z respectively. Otherembodiments may provide communication between a Client acting as amulti-chassis master and a plurality of SCMs via any networkconnectivity between the SCMs and the client, such as portions ofnetwork 1619. It is important only that the master Client establishlogical connectivity with a CM executing in each SCM included in eachrespective chassis of the multi-chassis system under management of themaster Client.

While the aforementioned multi-chassis system embodiments includeidentical chassis, other embodiments may include chassis of varyingcapabilities. For example, a first chassis in a multi-chassis system maynot include any FCMs, a second chassis may not include any OLBs, and athird chassis may include four OLBs. These and all other similarcombinations of compute, storage, and I/O resources are contemplated.Furthermore, embodiments of multi-chassis systems may include as few astwo chassis to tens, hundreds, or thousands of chassis, interconnectedwithout restriction via various combinations and topologies of LANs,WANs, MANs, and the Internet. In addition, multi-chassis management maybe performed via either or both of the two aforementioned variations andembodiments may include multiple instances of each variation operatingsubstantially in parallel, provisioning and managing a plurality ofprovisioned servers.

FIG. 17 illustrates an embodiment of two variations of multi-chassisprovisioning and management operations. Generally, in theClient-Mastered variation, a client (such as Client 1601A) acts as amaster for gathering information and distributing commands (rather thanrelying on an Enterprise Manager proxy). The client, acting as themaster, logically couples to a plurality of CMs executing on respectiveSCMs (such as SCMs 140X and 140Z). The CMs, acting as slaves,individually provide the information to the client (master) andindividually receive and act on the distributed commands from theclient.

Generally, in the Master-Free variation, a host Enterprise Managerexecuting on a host SCM operates as a proxy for receiving systeminformation from all chassis in the system, passing the information to aclient (such as Client 1601B) as necessary, depending on stateinformation required by the client. Such information may include eventinformation for processing with respect to queries, system statuschanges, or similar management and provisioning data. The hostEnterprise Manager further operates as a proxy for broadcasting ordistributing commands from Client 1601B to the proper chassis in thesystem. Such commands may include commands to provision or manageservers, or to perform other similar multi-chassis operations.

Communication of system information and commands between the hostEnterprise Manager and the other Enterprise Managers of themulti-chassis system is typically performed via an Open Shortest PathFirst (OSPF) protocol (an industry standard link-state protocol forrouting IP packets). An example of an OSPF protocol is described in “RFC2328—OSPF Version 2”, April 1998,(http://www.faqs.org/rfcs/rfc2328.html), herein incorporated byreference for all purposes. In some embodiments, data distribution isimplemented via extensions to an OSPF protocol, such as an opaque LinkStatus Advertisement (LSA) option (an industry standard technique ofdata distribution for arbitrary purposes throughout an OSPF domain). Anexample of an opaque LSA option extension is described in “RFC 2370—TheOSPF Opaque LSA Option”, July 1998,(http://www.faqs.org/rfcs/rfc2370.html), herein incorporated byreference for all purposes. Other embodiments communicate management andprovisioning information, events, commands, and other related data viaother OSPF-like protocols adapted for propagating and distributing datain an environment of dynamically varying bandwidth and topology.

With respect to OSPF processing, each ES system of the multi-chassissystem acts as a router, originating OSPF Link State Update messages(according to opaque LSAs, in some embodiments) indicating the currentstate of the respective ES system. The ES systems further operate topropagate similar information from adjacent ES systems (also acting asrouters with respect to OSPF processing) throughout the multi-chassissystem (often referred to as autonomous system in regards to OSPFoperations). The propagated information includes data values requiredfor proper determination and processing of server provisioning andmanagement operations, including data values referenced by queries beingmonitored for activation. For example, command execution results andmodule status changes (such as Module Operational Status Up/Down events,as described in the Selected BMC Event Details section, elsewhereherein) are packaged for dissemination via Link State Update messages,and provided to the adjacent ES systems. Since the Link State Updatemessages are communicated reliably (via the Link State Ackacknowledgement handshake), all ES systems in a multi-chassis systemhave access to reliable near real time status information for all of thechassis in the multi-chassis system. In some embodiments, OSPF Hello andLink State Request messages may be used to discover ES systems presentin the multi-chassis system.

Referring to FIG. 17, Master-Free Management Flow 1701 illustratesprocessing specific to an embodiment of the first variation, andClient-Mastered Management Flow 1702 illustrates processing specific toan embodiment of the second variation. The Master-Free flow starts at“Begin” 1701.1. The flow then continues to “Register to Receive OSPF ESInformation” 1701.2. Here the client (such as Client 1601B) registerswith a host enterprise management process executing on a host SCM (suchas SCM 140X) to receive and broadcast information via OSPF opaque LSAs,with the host enterprise management process acting as a proxy.Communication between the client and the host enterprise managementprocess is via coupling 1620, network 1619, and coupling 1614. The hostSCM in turn communicates with the other SCMs (or more specificallyenterprise management processes executing thereon) of the multi-chassissystem via network 1619 and coupling 1613, and optionally via coupling1616. Processing in “Register to Receive OSPF ES Information” 1701.2completes the Master-Free-specific portion of the overall flow.

The Client-Mastered flow starts at “Begin” 1702.1 and continues to“Connect to Next Chassis Manager” 1702.2. Here communication between theclient (such as client 1601A) and a CM process executing on the SCM ofthe first ES system (such as SCM 140X via coupling 1617) in themulti-chassis system is established. A check is then made to determineif connections have been established to all of the ES systems of themulti-chassis system at “Connected to All?” 1702.3. If there are moresystems to connect to, then flow proceeds along “No” 1702.3N back to1702.2 “Connect to Next Chassis Manager”. The next connection is thenestablished (such as to SCM 140Z via coupling 1618). If connections havebeen established to all desired ES systems of the multi-chassis system,then flow continues via “Yes” 1702.3Y, and the Client-Mastered-specificportion of the overall flow is complete.

Flow continues from “Register to Receive OSPF ES Information” 1701.2 andvia “Yes” 1702.3Y to “Monitor System Information” 1702.4, whereinformation received from each chassis of the multi-chassis system ismonitored. The Master-Free variation receives status change and eventinformation via the host enterprise management process, and the hostenterprise management process in turn collects the information via OSPFopaque LSA processing. The Client-Mastered variation receives theinformation directly from each chassis via the respective connectionsestablished in Client-Mastered Management Flow 1702.

In parallel with the system information monitoring, two other flows areoccurring, Monitor and Process Changes 1703 and Monitor User Interface1704. Generally, Monitor and Process Changes 1703 includes receiving andacting upon information collected from the system monitoring activity(status changes and events), including updating information displayed toone or more operators (such as users, system managers, and other relatedpersonnel). The functions further include processing queries and sendingcommands generated by any activated queries to member systems of themulti-chassis system that are required to execute the commands MonitorUser Interface 1704 includes waiting for commands from the operators(provided in response to the updating of information displayed, forexample) and distributing the commands to appropriate members of themulti-chassis system.

More specifically, information regarding status changes and events ispropagated to “Change?” 1703.1 from “Monitor System Information” 1702.4,as shown conceptually by dashed-arrow 1702.4C. “Change?” 1703.1determines if there has been a system status change or an event. If not(“No” 1703.1N), then processing loops back to “Change?” 1703.1. If therehas been a change or an event (“Yes” 1703.1Y), then flow continues to“Update Display” 1703.2., where the client updates any relevant displayinformation according to user interface requirements. Processing thenproceeds to “Process Queries” 1703.3, where queries are processed withrespect to the status changes and events, and commands may be formulatedin response to activated queries (similar to “Pre-Select Queries andRespond to Activated Queries” 1201.7 of FIG. 12A). Flow continues to“Broadcast Resultant Commands” 1703.4, where any resultant commands aredistributed to appropriate chassis, in a manner dependent on whether theoperating mode is the Master-Free or the Client-Mastered variation.After completion of command broadcast, flow returns to “Change?” 1703.1to await another status change or event.

“Broadcast Resultant Commands” 1703.4 processing, in the Master-Freevariation, unfolds in a two stage process. The commands are first sentfrom the client to the host enterprise management process, and then thecommands are broadcast via OSPF opaque LSAs to all of the managed ESsystems of the multi-chassis system. In the Client-Mastered variation,commands are broadcasted by the client to each managed ES system. Thebroadcasting may be performed directly by the client, using a form ofunicast transmission, or indirectly by the client using a form ofmulticast transmission, according to various embodiments.

Processing in “New Command?” 1704.1 determines if the operator hasprovided a command (frequently this occurs in response to changes indisplayed information, as indicated conceptually by dashed-arrow1703.2N). If not (“No” 1704.1N), then processing loops back to “NewCommand?” 1704.1. If a command has been received (“Yes” 1704.1Y), thenflow proceeds to “Process Command” 1704.2, where the operator command isprocessed into one or more commands for communication to the elements ofthe multi-chassis system. Processing continues in “Broadcast Command”1704.3, where the command (or commands) is sent to the appropriatemulti-chassis system members, in a variation dependent way, as in“Broadcast Resultant Commands” 1703.4.

In some embodiments, commands sent to the multi-chassis system (asgenerated by “Broadcast Resultant Commands” 1703.4 and “BroadcastCommand” 1704.3, for example), may be multi-stage commands (orsub-commands) requiring one or more synchronization events with respectto execution of sub-commands by members of the multi-chassis system.Synchronization may extend across any number and combination of themulti-chassis members, depending on specifics of the command, topologyof the multi-chassis system, and implementation specificcharacteristics.

Conclusion

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive. It will be understood that many variations in construction,arrangement and use are possible consistent with the teachings andwithin the scope of the claims appended to the issued patent. Forexample, interconnect and function-unit bit-widths, clock speeds, andthe type of technology used may generally be varied in each componentblock. Also, unless specifically stated to the contrary, the valueranges specified, the maximum and minimum values used, or otherparticular specifications (such as the quantity and type of processorsand memory on the modules, the channel bandwidths, the degree ofredundancy for any particular component or module, the particularversion of an interface standard or component, the number of entries ina buffer), are merely those of the illustrative embodiments, can beexpected to track improvements and changes in implementation technology,and should not be construed as limitations.

Functionally equivalent techniques known to those of ordinary skill inthe art may be employed instead of those illustrated to implementvarious components or sub-systems. The names given to interconnect andlogic are merely illustrative, and should not be construed as limitingthe concepts taught. It is also understood that many design functionalaspects may be carried out in either hardware (i.e., generally dedicatedcircuitry) or software (i.e., via some manner of programmed controlleror processor), as a function of implementation dependent designconstraints and the technology trends of faster processing (whichfacilitates migration of functions previously in hardware into software)and higher integration density (which facilitates migration of functionspreviously in software into hardware). Specific variations may include,but are not limited to: differences in module and chassis partitioning;different module and chassis form factors and configurations; use ofdifferent operating systems and other system software; use of differentinterface standards, network protocols, or communication links; andother variations to be expected when implementing the concepts taughtherein in accordance with the unique engineering and businessconstraints of a particular application.

The embodiments have been illustrated with detail and environmentalcontext well beyond that required for a minimal implementation of manyof aspects of the concepts taught. Those of ordinary skill in the artwill recognize that variations may omit disclosed components withoutaltering the basic cooperation among the remaining elements. It is thusunderstood that much of the details disclosed are not required toimplement various aspects of the concepts taught. To the extent that theremaining elements are distinguishable from the prior art, omittedcomponents are not limiting on the concepts taught herein.

All such variations in design comprise insubstantial changes over theteachings conveyed by the illustrative embodiments. It is alsounderstood that the concepts taught herein have broad applicability toother computing and networking applications, and are not limited to theparticular application or industry of the illustrated embodiments. Theinvention is thus to be construed as including all possiblemodifications and variations encompassed within the scope of the claimsappended to the issued patent.

1. A method including the steps of: communicating multi-chassis control instructions from a multi-chassis control agent to a portal multi-chassis platform process; distributing the multi-chassis control instructions from the portal multi-chassis platform process to a plurality of peer multi-chassis platform processes executing in a respective plurality of chassis; coalescing multi-chassis control data from the peer multi-chassis platform processes to the portal multi-chassis platform process; communicating the multi-chassis control data from the portal multi-chassis platform process to the multi-chassis control agent; wherein the multi-chassis control agent determines at least a portion of the multi-chassis control instructions based in part on at least a portion of the multi-chassis control data; and wherein at least one of the chassis includes at least a first partition of a plurality of partitionable symmetric multiprocessors, the multi-chassis control instructions include at least one instruction directed to the first partition, and the multi-chassis control data includes data from the first partition.
 2. The method of claim 1, wherein the distributing of the multi-chassis control instructions is at least in part via an open shortest path first protocol.
 3. The method of claim 1, wherein the coalescing of the multi-chassis control data is at least in part via an open shortest path first protocol.
 4. The method of claim 1, wherein each of the chassis includes a respective switch fabric and at least a portion of the multi-chassis control instructions are communicated in part via at least one of the switch fabrics.
 5. The method of claim 1, wherein each of the chassis includes a respective switch fabric and at least a portion of the multi-chassis control data is communicated in part via at least one of the switch fabrics.
 6. The method of claim 1, further including establishing logical communication between the multi-chassis control agent and the portal multi-chassis platform process.
 7. The method of claim 1, wherein the multi-chassis control agent executes a multi-chassis control process at least in part to determine the portion of the multi-chassis control instructions.
 8. The method of claim 1, wherein the multi-chassis control agent is a client.
 9. The method of claim 1, wherein the portal multi-chassis platform process is a host multi-chassis platform process.
 10. The method of claim 1, wherein at least one of the peer multi-chassis platform processes is a chassis manager process.
 11. The method of claim 1, wherein at least one of the peer multi-chassis platform processes is an enterprise manager process. 